Mailing List Archive: Cisco: NSP

SXI(3) code status?

Index | Next | Previous | View Threaded

jfitz at princeton

Nov 17, 2009, 6:51 AM

Post #1 of 21 (1575 views)
Permalink

SXI(3) code status?

I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.

Does anyone else have GOOD or BAD new on SXI(3)?

Jeff Fitzwater
OIT Network Systems
Princeton University

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

rubensk at gmail

Nov 17, 2009, 7:22 AM

Post #2 of 21 (1508 views)
Permalink

Re: SXI(3) code status? [In reply to]

SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.

Rubens

On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>
>
> Does anyone else have GOOD or BAD new on SXI(3)?
>
>
> Jeff Fitzwater
> OIT Network Systems
> Princeton University
>
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

jared at puck

Nov 17, 2009, 7:31 AM

Post #3 of 21 (1536 views)
Permalink

Re: SXI(3) code status? [In reply to]

SXI3 has a number of bug fixes for our network, including one that would cause the next-hop to be populated as 'drop' in hardware.

I strongly recommend using it over prior versions of SXI.

Due to the removal of hardware support we replaced the older 63xx/62xx series cards.

- Jared

On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:

> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>
>
> Rubens
>
>
>
> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>>
>>
>> Does anyone else have GOOD or BAD new on SXI(3)?
>>
>>
>> Jeff Fitzwater
>> OIT Network Systems
>> Princeton University
>>
>>
>>
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp [at] puck
>> 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
> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

cphillips at wbsconnect

Nov 17, 2009, 9:05 AM

Post #4 of 21 (1506 views)
Permalink

Re: SXI(3) code status? [In reply to]

Jared,

After quickly glancing at the release notes, I was unable to find
anything about the removal of hardware support for the 63xx series
cards. Do you have a URL or can you be more specific?

Thanks in advance!

Jared Mauch wrote:
> SXI3 has a number of bug fixes for our network, including one that would cause the next-hop to be populated as 'drop' in hardware.
>
> I strongly recommend using it over prior versions of SXI.
>
> Due to the removal of hardware support we replaced the older 63xx/62xx series cards.
>
> - Jared
>
> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>
>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>
>>
>> Rubens
>>
>>
>>
>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>>> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>>>
>>>
>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>
>>>
>>> Jeff Fitzwater
>>> OIT Network Systems
>>> Princeton University
>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-nsp mailing list cisco-nsp [at] puck
>>> 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
>> 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
> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

jared at puck

Nov 17, 2009, 9:12 AM

Post #5 of 21 (1504 views)
Permalink

Re: SXI(3) code status? [In reply to]

Release 12.2(33)SXH and later releases do not support the following hardware:

These Ethernet Switching Modules:

–WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ

–WS-X6248A-TEL 48-port 10/100TX RJ-21

–WS-X6248-RJ-45 48-port 10/100TX RJ-45

–WS-X6248-TEL 48-port 10/100TX RJ-21

–WS-X6324-100FX-SM 24-port 100FX Ethernet

–WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ

–WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45

–WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ

Now, the caveat is that they did not actually remove the hardware support for some of these until SXI1, so while the release notes say one thing, the actual support varies.

You will see something like this in 'show power':
4 WS-X6248A-TEL 112.98 2.69 - - on off (not supported)
8 WS-X6248-RJ-45 112.98 2.69 - - on off (not supported)

It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I can't recall if that was the case for SXI2/2a/or 1.

- Jared

On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:

> Jared,
>
> After quickly glancing at the release notes, I was unable to find anything about the removal of hardware support for the 63xx series cards. Do you have a URL or can you be more specific?
>
> Thanks in advance!
>
> Jared Mauch wrote:
>> SXI3 has a number of bug fixes for our network, including one that would cause the next-hop to be populated as 'drop' in hardware.
>> I strongly recommend using it over prior versions of SXI.
>> Due to the removal of hardware support we replaced the older 63xx/62xx series cards.
>> - Jared
>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>
>>>
>>> Rubens
>>>
>>>
>>>
>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>>>> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>>>>
>>>>
>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>
>>>>
>>>> Jeff Fitzwater
>>>> OIT Network Systems
>>>> Princeton University
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>> 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
>>> 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
>> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

jfitz at princeton

Nov 17, 2009, 11:34 AM

Post #6 of 21 (1491 views)
Permalink

Re: SXI(3) code status? [In reply to]

The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A. It did however work in SXI, which we are running now.

The other flavors are not supported.

Jeff

On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:

> Release 12.2(33)SXH and later releases do not support the following hardware:
>
> These Ethernet Switching Modules:
>
> –WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>
> –WS-X6248A-TEL 48-port 10/100TX RJ-21
>
> –WS-X6248-RJ-45 48-port 10/100TX RJ-45
>
> –WS-X6248-TEL 48-port 10/100TX RJ-21
>
> –WS-X6324-100FX-SM 24-port 100FX Ethernet
>
> –WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>
> –WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>
> –WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>
> Now, the caveat is that they did not actually remove the hardware support for some of these until SXI1, so while the release notes say one thing, the actual support varies.
>
> You will see something like this in 'show power':
> 4 WS-X6248A-TEL 112.98 2.69 - - on off (not supported)
> 8 WS-X6248-RJ-45 112.98 2.69 - - on off (not supported)
>
> It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I can't recall if that was the case for SXI2/2a/or 1.
>
> - Jared
>
> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>
>> Jared,
>>
>> After quickly glancing at the release notes, I was unable to find anything about the removal of hardware support for the 63xx series cards. Do you have a URL or can you be more specific?
>>
>> Thanks in advance!
>>
>> Jared Mauch wrote:
>>> SXI3 has a number of bug fixes for our network, including one that would cause the next-hop to be populated as 'drop' in hardware.
>>> I strongly recommend using it over prior versions of SXI.
>>> Due to the removal of hardware support we replaced the older 63xx/62xx series cards.
>>> - Jared
>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>
>>>>
>>>> Rubens
>>>>
>>>>
>>>>
>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>>>>> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>>>>>
>>>>>
>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>
>>>>>
>>>>> Jeff Fitzwater
>>>>> OIT Network Systems
>>>>> Princeton University
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>> 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
>>>> 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
>>> 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
> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

thehink at gmail

Nov 18, 2009, 1:38 AM

Post #7 of 21 (1496 views)
Permalink

Re: SXI(3) code status? [In reply to]

Here is some BAD on SXI3 ...

with redundant supervisor, SSH breaks upon supervisor switchover.

-andrew

On Tue, Nov 17, 2009 at 11:34 AM, Jeff Fitzwater <jfitz [at] princeton> wrote:
> The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A. It did however work in SXI, which we are running now.
>
> The other flavors are not supported.
>
> Jeff
>
> On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:
>
>> Release 12.2(33)SXH and later releases do not support the following hardware:
>>
>> These Ethernet Switching Modules:
>>
>> –WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>>
>> –WS-X6248A-TEL 48-port 10/100TX RJ-21
>>
>> –WS-X6248-RJ-45 48-port 10/100TX RJ-45
>>
>> –WS-X6248-TEL 48-port 10/100TX RJ-21
>>
>> –WS-X6324-100FX-SM 24-port 100FX Ethernet
>>
>> –WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>>
>> –WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>>
>> –WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>>
>> Now, the caveat is that they did not actually remove the hardware support for some of these until SXI1, so while the release notes say one thing, the actual support varies.
>>
>> You will see something like this in 'show power':
>> 4 WS-X6248A-TEL 112.98 2.69 - - on off (not supported)
>> 8 WS-X6248-RJ-45 112.98 2.69 - - on off (not supported)
>>
>> It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I can't recall if that was the case for SXI2/2a/or 1.
>>
>> - Jared
>>
>> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>>
>>> Jared,
>>>
>>> After quickly glancing at the release notes, I was unable to find anything about the removal of hardware support for the 63xx series cards. Do you have a URL or can you be more specific?
>>>
>>> Thanks in advance!
>>>
>>> Jared Mauch wrote:
>>>> SXI3 has a number of bug fixes for our network, including one that would cause the next-hop to be populated as 'drop' in hardware.
>>>> I strongly recommend using it over prior versions of SXI.
>>>> Due to the removal of hardware support we replaced the older 63xx/62xx series cards.
>>>> - Jared
>>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>>
>>>>>
>>>>> Rubens
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>>>>>> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>>>>>>
>>>>>>
>>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>>
>>>>>>
>>>>>> Jeff Fitzwater
>>>>>> OIT Network Systems
>>>>>> Princeton University
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>>> 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
>>>>> 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
>>>> 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
>> 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
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

--
-andrew
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

cphillips at wbsconnect

Nov 18, 2009, 2:00 AM

Post #8 of 21 (1475 views)
Permalink

Re: SXI(3) code status? [In reply to]

Define breaks. Breaks as in your ssh connection drops and you have to
login again, or breaks as in your ssh connection drops and the ssh
service doesn't restart?

andrew wrote:
> Here is some BAD on SXI3 ...
>
> with redundant supervisor, SSH breaks upon supervisor switchover.
>
> -andrew
>
> On Tue, Nov 17, 2009 at 11:34 AM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>> The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A. It did however work in SXI, which we are running now.
>>
>> The other flavors are not supported.
>>
>> Jeff
>>
>> On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:
>>
>>> Release 12.2(33)SXH and later releases do not support the following hardware:
>>>
>>> These Ethernet Switching Modules:
>>>
>>> –WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>>>
>>> –WS-X6248A-TEL 48-port 10/100TX RJ-21
>>>
>>> –WS-X6248-RJ-45 48-port 10/100TX RJ-45
>>>
>>> –WS-X6248-TEL 48-port 10/100TX RJ-21
>>>
>>> –WS-X6324-100FX-SM 24-port 100FX Ethernet
>>>
>>> –WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>>>
>>> –WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>>>
>>> –WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>>>
>>> Now, the caveat is that they did not actually remove the hardware support for some of these until SXI1, so while the release notes say one thing, the actual support varies.
>>>
>>> You will see something like this in 'show power':
>>> 4 WS-X6248A-TEL 112.98 2.69 - - on off (not supported)
>>> 8 WS-X6248-RJ-45 112.98 2.69 - - on off (not supported)
>>>
>>> It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I can't recall if that was the case for SXI2/2a/or 1.
>>>
>>> - Jared
>>>
>>> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>>>
>>>> Jared,
>>>>
>>>> After quickly glancing at the release notes, I was unable to find anything about the removal of hardware support for the 63xx series cards. Do you have a URL or can you be more specific?
>>>>
>>>> Thanks in advance!
>>>>
>>>> Jared Mauch wrote:
>>>>> SXI3 has a number of bug fixes for our network, including one that would cause the next-hop to be populated as 'drop' in hardware.
>>>>> I strongly recommend using it over prior versions of SXI.
>>>>> Due to the removal of hardware support we replaced the older 63xx/62xx series cards.
>>>>> - Jared
>>>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>>>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>>>
>>>>>>
>>>>>> Rubens
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater <jfitz [at] princeton> wrote:
>>>>>>> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>>>>>>>
>>>>>>>
>>>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>>>
>>>>>>>
>>>>>>> Jeff Fitzwater
>>>>>>> OIT Network Systems
>>>>>>> Princeton University
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>>>> 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
>>>>>> 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
>>>>> 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
>>> 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
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
>
>

--
Chris Phillips
Director of Network Engineering & Peering Coordinator
WBS Connect
cphillips [at] wbsconnect
(866) WBS-CONX
(720) 259-8361 - direct
(303) 968-4383 - mobile
www.wbsconnect.com
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

mtinka at globaltransit

Nov 18, 2009, 2:15 AM

Post #9 of 21 (1498 views)
Permalink

Re: SXI(3) code status? [In reply to]

On Tuesday 17 November 2009 11:31:18 pm Jared Mauch wrote:

> I strongly recommend using it over prior versions of SXI.

As part of our recent round of upgrades, we moved from SXH3
to SXI2a. It did fix a non-severe AAA bug we hit when we
first moved to SXH3.

If we'd waited 4 extra days, we'd have rolled over to SXI3
instead, but for our applications (pure Layer 2 Ethernet
switching with the boxes running as an IS-IS DIS), SXI2a
should be super-stable for us for another 10 years, even
(okay, maybe not, hehe). Newer line cards notwithstanding,
if it weren't for the AAA bug, we'd probably have stayed on
SXH3 also (which served us well for some 1.3 years).

We simply aren't using any of the other features to run any
potentially crippling kinky stuff on the box.

Cheers,

Mark.

Attachments:

signature.asc (0.82 KB)

thehink at gmail

Nov 18, 2009, 2:29 AM

Post #10 of 21 (1473 views)
Permalink

Re: SXI(3) code status? [In reply to]

Breaks as in after forcing a sup switchover while on console
subsequent SSH connections are refused, as it seems the private key is
missing/unreadable.

This is logged:

Nov 18 10:16:08.211: SSH2 0: RSA_sign: private key not found
Nov 18 10:16:08.211: SSH2 0: signature creation failed, status -1

Clearing RSA keys and re-generating did not help.

Clear RSA keys, *reboot box*, and re-generate did fix.

On Wed, Nov 18, 2009 at 2:00 AM, Chris Phillips
<cphillips [at] wbsconnect> wrote:
> Define breaks. Breaks as in your ssh connection drops and you have to login
> again, or breaks as in your ssh connection drops and the ssh service doesn't
> restart?
>
> andrew wrote:
>>
>> Here is some BAD on SXI3 ...
>>
>> with redundant supervisor, SSH breaks upon supervisor switchover.
>>
>> -andrew
>>
>> On Tue, Nov 17, 2009 at 11:34 AM, Jeff Fitzwater <jfitz [at] princeton>
>> wrote:
>>>
>>> The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A. It
>>> did however work in SXI, which we are running now.
>>>
>>> The other flavors are not supported.
>>>
>>> Jeff
>>>
>>> On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:
>>>
>>>> Release 12.2(33)SXH and later releases do not support the following
>>>> hardware:
>>>>
>>>> These Ethernet Switching Modules:
>>>>
>>>> –WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>>>>
>>>> –WS-X6248A-TEL 48-port 10/100TX RJ-21
>>>>
>>>> –WS-X6248-RJ-45 48-port 10/100TX RJ-45
>>>>
>>>> –WS-X6248-TEL 48-port 10/100TX RJ-21
>>>>
>>>> –WS-X6324-100FX-SM 24-port 100FX Ethernet
>>>>
>>>> –WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>>>>
>>>> –WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>>>>
>>>> –WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>>>>
>>>> Now, the caveat is that they did not actually remove the hardware
>>>> support for some of these until SXI1, so while the release notes say one
>>>> thing, the actual support varies.
>>>>
>>>> You will see something like this in 'show power':
>>>> 4 WS-X6248A-TEL 112.98 2.69 - - on off (not
>>>> supported)
>>>> 8 WS-X6248-RJ-45 112.98 2.69 - - on off (not
>>>> supported)
>>>>
>>>> It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I
>>>> can't recall if that was the case for SXI2/2a/or 1.
>>>>
>>>> - Jared
>>>>
>>>> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>>>>
>>>>> Jared,
>>>>>
>>>>> After quickly glancing at the release notes, I was unable to find
>>>>> anything about the removal of hardware support for the 63xx series cards.
>>>>> Do you have a URL or can you be more specific?
>>>>>
>>>>> Thanks in advance!
>>>>>
>>>>> Jared Mauch wrote:
>>>>>>
>>>>>> SXI3 has a number of bug fixes for our network, including one that
>>>>>> would cause the next-hop to be populated as 'drop' in hardware.
>>>>>> I strongly recommend using it over prior versions of SXI.
>>>>>> Due to the removal of hardware support we replaced the older 63xx/62xx
>>>>>> series cards.
>>>>>> - Jared
>>>>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>>>>>
>>>>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>>>>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>>>>
>>>>>>>
>>>>>>> Rubens
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater
>>>>>>> <jfitz [at] princeton> wrote:
>>>>>>>>
>>>>>>>> I have been running the SXI(3) on a test router with 100M MM 6324,
>>>>>>>> which it did not recognize in previous versions, and so far no complaints
>>>>>>>> but then again it's not in a real world yet.
>>>>>>>>
>>>>>>>>
>>>>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>>>>
>>>>>>>>
>>>>>>>> Jeff Fitzwater
>>>>>>>> OIT Network Systems
>>>>>>>> Princeton University
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>>>>> 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
>>>>>>> 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
>>>>>> 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
>>>> 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
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>
>>
>>
>
> --
> Chris Phillips
> Director of Network Engineering & Peering Coordinator
> WBS Connect
> cphillips [at] wbsconnect
> (866) WBS-CONX
> (720) 259-8361 - direct
> (303) 968-4383 - mobile
> www.wbsconnect.com
>

--
-andrew
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reinhold.Fischer at gmx

Nov 18, 2009, 2:30 AM

Post #11 of 21 (1500 views)
Permalink

Re: SXI(3) code status? [In reply to]

We upgraded tonight one of our boxes to SXI3. The WS-X6324-100FX-MM works with this version of code!

hth, Reinhold

On Tue, Nov 17, 2009 at 09:51:01AM -0500, Jeff Fitzwater wrote:
> I have been running the SXI(3) on a test router with 100M MM 6324, which it did not recognize in previous versions, and so far no complaints but then again it's not in a real world yet.
>
>
> Does anyone else have GOOD or BAD new on SXI(3)?
>
>
> Jeff Fitzwater
> OIT Network Systems
> Princeton University
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

tomas at soitron

Nov 18, 2009, 2:40 AM

Post #12 of 21 (1474 views)
Permalink

Re: SXI(3) code status? [In reply to]

> -----Original Message-----
> From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-
> bounces [at] puck] On Behalf Of Mark Tinka
> Sent: Wednesday, November 18, 2009 11:15 AM
> To: cisco-nsp [at] puck
> Cc: Jared Mauch
> Subject: Re: [c-nsp] SXI(3) code status?
>
> On Tuesday 17 November 2009 11:31:18 pm Jared Mauch wrote:
>
> > I strongly recommend using it over prior versions of SXI.
>
> As part of our recent round of upgrades, we moved from SXH3
> to SXI2a. It did fix a non-severe AAA bug we hit when we
> first moved to SXH3.

Which one that was? We've been hit by a bug when using TAC+ out of a
VRF. Initial user authentication is OK, but the subsequent enable auth
outgoing packets do not have the proper VRF set and go out the GRT
instead. Funny enough, the return packet returns via the VRF and the box
eats it.

We've filed CSCtc86306 for this hoping to have this fixed by SXI3, but
after exchanging lots of e-mails with India TAC the status was that they
do understand the issue and suddenly they've just stated it works as
expected. The SXI3 goal is missed now, and ages to come until the next
maintenance build...

Aug 28 17:00:37.285: AAA/MEMORY: create_user (0xF7E8CF8) user='xxxxxxxx'
ruser='NULL' ds0=0 port='tty2' rem_addr='x.x.x.x' authen_type=ASCII
service=ENABLE priv=15 initial_task_id='0', vrf= (id=0) <=== they
somehow forgot to fill this in for enable auth

--

deejay

__________ Informacia od ESET NOD32 Antivirus, verzia databazy 4616
(20091117) __________

Tuto spravu preveril ESET NOD32 Antivirus.

http://www.eset.sk

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

mtinka at globaltransit

Nov 18, 2009, 3:01 AM

Post #13 of 21 (1486 views)
Permalink

Re: SXI(3) code status? [In reply to]

On Wednesday 18 November 2009 06:40:39 pm Daniska, Tomas
wrote:

> Which one that was? We've been hit by a bug when using
> TAC+ out of a VRF. Initial user authentication is OK, but
> the subsequent enable auth outgoing packets do not have
> the proper VRF set and go out the GRT instead. Funny
> enough, the return packet returns via the VRF and the box
> eats it.

In our case, using TACACS+ also, initial user
authentications works fine, but the switch refuses to
authenticate against the regular enable password and instead
chooses the fallback password.

In all honesty, we didn't debug this for too long because we
only have 4 units in operation (core), were too busy with
other stuff, and we could just work around it by adjusting
RANCID's .cloginrc details (which were the most important).

The issue is fixed in SXI2a (perhaps even earlier, in later
versions post SXH3), and we didn't do anything to our
TACACS+ backend.

Cheers,

Mark.

Attachments:

signature.asc (0.82 KB)

William.Murphy at uth

Nov 18, 2009, 9:10 AM

Post #14 of 21 (1488 views)
Permalink

Re: SXI(3) code status? [In reply to]

We have VSS running so would the same apply if I force switchover with VSS?
Is it only "redundancy force-switchover" command or will failover for other
cause yield same result?

Thanks...

Bill

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of andrew
Sent: Wednesday, November 18, 2009 4:29 AM
To: Chris Phillips
Cc: cisco-nsp [at] puck; Jared Mauch
Subject: Re: [c-nsp] SXI(3) code status?

Breaks as in after forcing a sup switchover while on console
subsequent SSH connections are refused, as it seems the private key is
missing/unreadable.

This is logged:

Nov 18 10:16:08.211: SSH2 0: RSA_sign: private key not found
Nov 18 10:16:08.211: SSH2 0: signature creation failed, status -1

Clearing RSA keys and re-generating did not help.

Clear RSA keys, *reboot box*, and re-generate did fix.

On Wed, Nov 18, 2009 at 2:00 AM, Chris Phillips
<cphillips [at] wbsconnect> wrote:
> Define breaks. Breaks as in your ssh connection drops and you have to
login
> again, or breaks as in your ssh connection drops and the ssh service
doesn't
> restart?
>
> andrew wrote:
>>
>> Here is some BAD on SXI3 ...
>>
>> with redundant supervisor, SSH breaks upon supervisor switchover.
>>
>> -andrew
>>
>> On Tue, Nov 17, 2009 at 11:34 AM, Jeff Fitzwater <jfitz [at] princeton>
>> wrote:
>>>
>>> The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A.
It
>>> did however work in SXI, which we are running now.
>>>
>>> The other flavors are not supported.
>>>
>>> Jeff
>>>
>>> On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:
>>>
>>>> Release 12.2(33)SXH and later releases do not support the following
>>>> hardware:
>>>>
>>>> These Ethernet Switching Modules:
>>>>
>>>> –WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>>>>
>>>> –WS-X6248A-TEL 48-port 10/100TX RJ-21
>>>>
>>>> –WS-X6248-RJ-45 48-port 10/100TX RJ-45
>>>>
>>>> –WS-X6248-TEL 48-port 10/100TX RJ-21
>>>>
>>>> –WS-X6324-100FX-SM 24-port 100FX Ethernet
>>>>
>>>> –WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>>>>
>>>> –WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>>>>
>>>> –WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>>>>
>>>> Now, the caveat is that they did not actually remove the hardware
>>>> support for some of these until SXI1, so while the release notes say
one
>>>> thing, the actual support varies.
>>>>
>>>> You will see something like this in 'show power':
>>>> 4 WS-X6248A-TEL 112.98 2.69 - - on off (not
>>>> supported)
>>>> 8 WS-X6248-RJ-45 112.98 2.69 - - on off (not
>>>> supported)
>>>>
>>>> It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I
>>>> can't recall if that was the case for SXI2/2a/or 1.
>>>>
>>>> - Jared
>>>>
>>>> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>>>>
>>>>> Jared,
>>>>>
>>>>> After quickly glancing at the release notes, I was unable to find
>>>>> anything about the removal of hardware support for the 63xx series
cards.
>>>>> Do you have a URL or can you be more specific?
>>>>>
>>>>> Thanks in advance!
>>>>>
>>>>> Jared Mauch wrote:
>>>>>>
>>>>>> SXI3 has a number of bug fixes for our network, including one that
>>>>>> would cause the next-hop to be populated as 'drop' in hardware.
>>>>>> I strongly recommend using it over prior versions of SXI.
>>>>>> Due to the removal of hardware support we replaced the older
63xx/62xx
>>>>>> series cards.
>>>>>> - Jared
>>>>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>>>>>
>>>>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>>>>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>>>>
>>>>>>>
>>>>>>> Rubens
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater
>>>>>>> <jfitz [at] princeton> wrote:
>>>>>>>>
>>>>>>>> I have been running the SXI(3) on a test router with 100M MM 6324,
>>>>>>>> which it did not recognize in previous versions, and so far no
complaints
>>>>>>>> but then again it's not in a real world yet.
>>>>>>>>
>>>>>>>>
>>>>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>>>>
>>>>>>>>
>>>>>>>> Jeff Fitzwater
>>>>>>>> OIT Network Systems
>>>>>>>> Princeton University
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>>>>> 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
>>>>>>> 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
>>>>>> 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
>>>> 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
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>
>>
>>
>
> --
> Chris Phillips
> Director of Network Engineering & Peering Coordinator
> WBS Connect
> cphillips [at] wbsconnect
> (866) WBS-CONX
> (720) 259-8361 - direct
> (303) 968-4383 - mobile
> www.wbsconnect.com
>

--
-andrew
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Attachments:

smime.p7s (4.23 KB)

tdurack at gmail

Nov 18, 2009, 12:39 PM

Post #15 of 21 (1473 views)
Permalink

Re: SXI(3) code status? [In reply to]

SXI3 has also removed "patching" ability:

"Installer/patching capability is removed starting from some of the
new images in SXI. Installer patching support will continue on SXH and
SXF. For Cisco IOS 12.2(33)SXI3, ION patching is no longer supported."

Not that patching has ever really been supported in any meaningful
fashion (when was the last time you found a patch to apply?)

Would be real nice if the release notes actually specified some of
this stuff, instead of us having to dig around and find.

Would be even better if Cisco admitted defeat and ported NX-OS to C6K...

Tim:>

On Wed, Nov 18, 2009 at 12:10 PM, Murphy, William
<William.Murphy [at] uth> wrote:
> We have VSS running so would the same apply if I force switchover with VSS?
> Is it only "redundancy force-switchover" command or will failover for other
> cause yield same result?
>
> Thanks...
>
> Bill
>
> -----Original Message-----
> From: cisco-nsp-bounces [at] puck
> [mailto:cisco-nsp-bounces [at] puck] On Behalf Of andrew
> Sent: Wednesday, November 18, 2009 4:29 AM
> To: Chris Phillips
> Cc: cisco-nsp [at] puck; Jared Mauch
> Subject: Re: [c-nsp] SXI(3) code status?
>
> Breaks as in after forcing a sup switchover while on console
> subsequent SSH connections are refused, as it seems the private key is
> missing/unreadable.
>
>
> This is logged:
>
> Nov 18 10:16:08.211: SSH2 0: RSA_sign: private key not found
> Nov 18 10:16:08.211: SSH2 0: signature creation failed, status -1
>
>
> Clearing RSA keys and re-generating did not help.
>
> Clear RSA keys, *reboot box*, and re-generate did fix.
>
>
>
>
>
> On Wed, Nov 18, 2009 at 2:00 AM, Chris Phillips
> <cphillips [at] wbsconnect> wrote:
>> Define breaks. Breaks as in your ssh connection drops and you have to
> login
>> again, or breaks as in your ssh connection drops and the ssh service
> doesn't
>> restart?
>>
>> andrew wrote:
>>>
>>> Here is some BAD on SXI3 ...
>>>
>>> with redundant supervisor, SSH breaks upon supervisor switchover.
>>>
>>> -andrew
>>>
>>> On Tue, Nov 17, 2009 at 11:34 AM, Jeff Fitzwater <jfitz [at] princeton>
>>> wrote:
>>>>
>>>> The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A.
> It
>>>> did however work in SXI, which we are running now.
>>>>
>>>> The other flavors are not supported.
>>>>
>>>> Jeff
>>>>
>>>> On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:
>>>>
>>>>> Release 12.2(33)SXH and later releases do not support the following
>>>>> hardware:
>>>>>
>>>>> These Ethernet Switching Modules:
>>>>>
>>>>> –WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>>>>>
>>>>> –WS-X6248A-TEL 48-port 10/100TX RJ-21
>>>>>
>>>>> –WS-X6248-RJ-45 48-port 10/100TX RJ-45
>>>>>
>>>>> –WS-X6248-TEL 48-port 10/100TX RJ-21
>>>>>
>>>>> –WS-X6324-100FX-SM 24-port 100FX Ethernet
>>>>>
>>>>> –WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>>>>>
>>>>> –WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>>>>>
>>>>> –WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>>>>>
>>>>> Now, the caveat is that they did not actually remove the hardware
>>>>> support for some of these until SXI1, so while the release notes say
> one
>>>>> thing, the actual support varies.
>>>>>
>>>>> You will see something like this in 'show power':
>>>>> 4 WS-X6248A-TEL 112.98 2.69 - - on off (not
>>>>> supported)
>>>>> 8 WS-X6248-RJ-45 112.98 2.69 - - on off (not
>>>>> supported)
>>>>>
>>>>> It does appear the WS-X6324-100FX-MM card does power on for SXI3, but I
>>>>> can't recall if that was the case for SXI2/2a/or 1.
>>>>>
>>>>> - Jared
>>>>>
>>>>> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>>>>>
>>>>>> Jared,
>>>>>>
>>>>>> After quickly glancing at the release notes, I was unable to find
>>>>>> anything about the removal of hardware support for the 63xx series
> cards.
>>>>>> Do you have a URL or can you be more specific?
>>>>>>
>>>>>> Thanks in advance!
>>>>>>
>>>>>> Jared Mauch wrote:
>>>>>>>
>>>>>>> SXI3 has a number of bug fixes for our network, including one that
>>>>>>> would cause the next-hop to be populated as 'drop' in hardware.
>>>>>>> I strongly recommend using it over prior versions of SXI.
>>>>>>> Due to the removal of hardware support we replaced the older
> 63xx/62xx
>>>>>>> series cards.
>>>>>>> - Jared
>>>>>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>>>>>>
>>>>>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those... :-(),
>>>>>>>> OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>>>>>
>>>>>>>>
>>>>>>>> Rubens
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater
>>>>>>>> <jfitz [at] princeton> wrote:
>>>>>>>>>
>>>>>>>>> I have been running the SXI(3) on a test router with 100M MM 6324,
>>>>>>>>> which it did not recognize in previous versions, and so far no
> complaints
>>>>>>>>> but then again it's not in a real world yet.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Jeff Fitzwater
>>>>>>>>> OIT Network Systems
>>>>>>>>> Princeton University
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>>>>>> 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
>>>>>>>> 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
>>>>>>> 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
>>>>> 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
>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>>
>>>
>>>
>>>
>>
>> --
>> Chris Phillips
>> Director of Network Engineering & Peering Coordinator
>> WBS Connect
>> cphillips [at] wbsconnect
>> (866) WBS-CONX
>> (720) 259-8361 - direct
>> (303) 968-4383 - mobile
>> www.wbsconnect.com
>>
>
>
>
> --
> -andrew
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> 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
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

--
Tim:>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

gert at greenie

Nov 18, 2009, 2:14 PM

Post #16 of 21 (1497 views)
Permalink

Re: SXI(3) code status? [In reply to]

Hi,

On Wed, Nov 18, 2009 at 03:39:44PM -0500, Tim Durack wrote:
> SXI3 has also removed "patching" ability:
>
> "Installer/patching capability is removed starting from some of the
> new images in SXI. Installer patching support will continue on SXH and
> SXF. For Cisco IOS 12.2(33)SXI3, ION patching is no longer supported."

Hooray. There goes the hope that ION will eventually fulfill the
original promise "BGP bug? no problem, install patch, restart bgpd, no
reboot needed"...

> Would be even better if Cisco admitted defeat and ported NX-OS to C6K...

Indeed.

gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert [at] greenie
fax: +49-89-35655025 gert [at] net

Christophe.Cardon at bec

Nov 19, 2009, 12:34 AM

Post #17 of 21 (1463 views)
Permalink

Re: SXI(3) code status? [In reply to]

You are hitting bug id CSCtd21722 which we have reported to Cisco last week.

Problem also with SNMP ACL bypass with SXI3 on VSS setup. If you configure ACL to protect access to SNMP RO or RW, the ACL is not filtering and access is granted to anyone (if you know the community string of course).

-----Oprindelig meddelelse-----
Fra: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] På vegne af Murphy, William
Sendt: 18. november 2009 18:10
Til: andrew; Chris Phillips
Cc: cisco-nsp [at] puck; Jared Mauch
Emne: Re: [c-nsp] SXI(3) code status?

We have VSS running so would the same apply if I force switchover with VSS?
Is it only "redundancy force-switchover" command or will failover for other cause yield same result?

Thanks...

Bill

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of andrew
Sent: Wednesday, November 18, 2009 4:29 AM
To: Chris Phillips
Cc: cisco-nsp [at] puck; Jared Mauch
Subject: Re: [c-nsp] SXI(3) code status?

Breaks as in after forcing a sup switchover while on console subsequent SSH connections are refused, as it seems the private key is missing/unreadable.

This is logged:

Nov 18 10:16:08.211: SSH2 0: RSA_sign: private key not found Nov 18 10:16:08.211: SSH2 0: signature creation failed, status -1

Clearing RSA keys and re-generating did not help.

Clear RSA keys, *reboot box*, and re-generate did fix.

On Wed, Nov 18, 2009 at 2:00 AM, Chris Phillips <cphillips [at] wbsconnect> wrote:
> Define breaks. Breaks as in your ssh connection drops and you have to
login
> again, or breaks as in your ssh connection drops and the ssh service
doesn't
> restart?
>
> andrew wrote:
>>
>> Here is some BAD on SXI3 ...
>>
>> with redundant supervisor, SSH breaks upon supervisor switchover.
>>
>> -andrew
>>
>> On Tue, Nov 17, 2009 at 11:34 AM, Jeff Fitzwater
>> <jfitz [at] princeton>
>> wrote:
>>>
>>> The 6324 100 MM is supported but did not come online in SXI 1, 2 , 2A.
It
>>> did however work in SXI, which we are running now.
>>>
>>> The other flavors are not supported.
>>>
>>> Jeff
>>>
>>> On Nov 17, 2009, at 12:12 PM, Jared Mauch wrote:
>>>
>>>> Release 12.2(33)SXH and later releases do not support the following
>>>> hardware:
>>>>
>>>> These Ethernet Switching Modules:
>>>>
>>>> -WS-X6024-10FL-MT 24-port 10BASE-FL MT-RJ
>>>>
>>>> -WS-X6248A-TEL 48-port 10/100TX RJ-21
>>>>
>>>> -WS-X6248-RJ-45 48-port 10/100TX RJ-45
>>>>
>>>> -WS-X6248-TEL 48-port 10/100TX RJ-21
>>>>
>>>> -WS-X6324-100FX-SM 24-port 100FX Ethernet
>>>>
>>>> -WS-X6224-100FX-MT 24-port 100FX Ethernet Multimode MT-RJ
>>>>
>>>> -WS-X6316-GE-TX 16-port Gigabit Ethernet RJ-45
>>>>
>>>> -WS-X6416-GE-MT 16-Port Gigabit Ethernet MT-RJ
>>>>
>>>> Now, the caveat is that they did not actually remove the
>>>> hardware support for some of these until SXI1, so while the release
>>>> notes say
one
>>>> thing, the actual support varies.
>>>>
>>>> You will see something like this in 'show power':
>>>> 4 WS-X6248A-TEL 112.98 2.69 - - on off
>>>> (not
>>>> supported)
>>>> 8 WS-X6248-RJ-45 112.98 2.69 - - on off
>>>> (not
>>>> supported)
>>>>
>>>> It does appear the WS-X6324-100FX-MM card does power on for SXI3,
>>>> but I can't recall if that was the case for SXI2/2a/or 1.
>>>>
>>>> - Jared
>>>>
>>>> On Nov 17, 2009, at 12:05 PM, Chris Phillips wrote:
>>>>
>>>>> Jared,
>>>>>
>>>>> After quickly glancing at the release notes, I was unable to find
>>>>> anything about the removal of hardware support for the 63xx series
cards.
>>>>> Do you have a URL or can you be more specific?
>>>>>
>>>>> Thanks in advance!
>>>>>
>>>>> Jared Mauch wrote:
>>>>>>
>>>>>> SXI3 has a number of bug fixes for our network, including one
>>>>>> that would cause the next-hop to be populated as 'drop' in hardware.
>>>>>> I strongly recommend using it over prior versions of SXI.
>>>>>> Due to the removal of hardware support we replaced the older
63xx/62xx
>>>>>> series cards.
>>>>>> - Jared
>>>>>> On Nov 17, 2009, at 10:22 AM, Rubens Kuhl wrote:
>>>>>>>
>>>>>>> SXI2a running fine with MPLS, QoS, SVIs (no BFD on those...
>>>>>>> :-(), OSPF, BGP. PFC3C-only, no WAN cards/modules, no DFC.
>>>>>>>
>>>>>>>
>>>>>>> Rubens
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 17, 2009 at 12:51 PM, Jeff Fitzwater
>>>>>>> <jfitz [at] princeton> wrote:
>>>>>>>>
>>>>>>>> I have been running the SXI(3) on a test router with 100M MM
>>>>>>>> 6324, which it did not recognize in previous versions, and so
>>>>>>>> far no
complaints
>>>>>>>> but then again it's not in a real world yet.
>>>>>>>>
>>>>>>>>
>>>>>>>> Does anyone else have GOOD or BAD new on SXI(3)?
>>>>>>>>
>>>>>>>>
>>>>>>>> Jeff Fitzwater
>>>>>>>> OIT Network Systems
>>>>>>>> Princeton University
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> cisco-nsp mailing list cisco-nsp [at] puck
>>>>>>>> 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
>>>>>>> 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
>>>>>> 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
>>>> 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
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>
>>
>>
>
> --
> Chris Phillips
> Director of Network Engineering & Peering Coordinator WBS Connect
> cphillips [at] wbsconnect
> (866) WBS-CONX
> (720) 259-8361 - direct
> (303) 968-4383 - mobile
> www.wbsconnect.com
>

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

kgraham at industrial-marshmallow

Nov 19, 2009, 9:09 PM

Post #18 of 21 (1472 views)
Permalink

Re: SXI(3) code status? [In reply to]

> Problem also with SNMP ACL bypass with SXI3 on VSS setup. If you configure ACL

> to protect access to SNMP RO or RW, the ACL is not filtering and access is
> granted to anyone (if you know the community string of course).

Ouch, will want to track this before moving off of SXH rebuilds and SXI2a... Do
you have the bugid for that (presumably not present pre-SXI3)?
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

geert.nijs at gmail

Nov 19, 2009, 11:39 PM

Post #19 of 21 (1466 views)
Permalink

Re: SXI(3) code status? [In reply to]

i am also interested in a bug id. i am running the same setup, still version
SXI1, but has been running fine.
yet another thing for me on my to-do-list: verify this on sxi1

regards,
Geert

2009/11/20 Kevin Graham <kgraham [at] industrial-marshmallow>

>
>
> > Problem also with SNMP ACL bypass with SXI3 on VSS setup. If you
> configure ACL
>
> > to protect access to SNMP RO or RW, the ACL is not filtering and access
> is
> > granted to anyone (if you know the community string of course).
>
> Ouch, will want to track this before moving off of SXH rebuilds and
> SXI2a... Do
> you have the bugid for that (presumably not present pre-SXI3)?
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Christophe.Cardon at bec

Nov 20, 2009, 12:48 AM

Post #20 of 21 (1450 views)
Permalink

Re: SXI(3) code status? [In reply to]

Bug id is CSCee55603

We have found it in SXI2a and is still in SXI3. Cisco TAC says that the fix for the bug will be integrated in SXI4 which is planned for 2010.

________________________________
Fra: Geert Nijs [mailto:geert.nijs [at] gmail]
Sendt: 20. november 2009 08:39
Til: Kevin Graham
Cc: Christophe Cardon; cisco-nsp [at] puck
Emne: Re: [c-nsp] SXI(3) code status?

i am also interested in a bug id. i am running the same setup, still version SXI1, but has been running fine.
yet another thing for me on my to-do-list: verify this on sxi1

regards,
Geert

2009/11/20 Kevin Graham <kgraham [at] industrial-marshmallow<mailto:kgraham [at] industrial-marshmallow>>

> Problem also with SNMP ACL bypass with SXI3 on VSS setup. If you configure ACL

> to protect access to SNMP RO or RW, the ACL is not filtering and access is
> granted to anyone (if you know the community string of course).

Ouch, will want to track this before moving off of SXH rebuilds and SXI2a... Do
you have the bugid for that (presumably not present pre-SXI3)?
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck<mailto:cisco-nsp [at] puck>
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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

geert.nijs at gmail

Nov 20, 2009, 3:12 AM

Post #21 of 21 (1446 views)
Permalink

Re: SXI(3) code status? [In reply to]

ok, i verified the bug id, but it is clearly related to VRFs. In my case, i
am not yet using VRFs, so i should be safe:
just verified on SXI1 code and SNMP ACL works (again: no VRFs configured).

regards,
Geert

2009/11/20 Christophe Cardon <Christophe.Cardon [at] bec>

> Bug id is CSCee55603
>
> We have found it in SXI2a and is still in SXI3. Cisco TAC says that the
> fix for the bug will be integrated in SXI4 which is planned for 2010.
>
> ------------------------------
> *Fra:* Geert Nijs [mailto:geert.nijs [at] gmail]
> *Sendt:* 20. november 2009 08:39
> *Til:* Kevin Graham
> *Cc:* Christophe Cardon; cisco-nsp [at] puck
> *Emne:* Re: [c-nsp] SXI(3) code status?
>
> i am also interested in a bug id. i am running the same setup, still
> version SXI1, but has been running fine.
> yet another thing for me on my to-do-list: verify this on sxi1
>
> regards,
> Geert
>
> 2009/11/20 Kevin Graham <kgraham [at] industrial-marshmallow>
>
>>
>>
>> > Problem also with SNMP ACL bypass with SXI3 on VSS setup. If you
>> configure ACL
>>
>> > to protect access to SNMP RO or RW, the ACL is not filtering and access
>> is
>> > granted to anyone (if you know the community string of course).
>>
>> Ouch, will want to track this before moving off of SXH rebuilds and
>> SXI2a... Do
>> you have the bugid for that (presumably not present pre-SXI3)?
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp [at] puck
>> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads