SPA scale options on SIP-400

Hi All,
Are there any scalability limitations on 7600 with a SIP-400 module?
Specifically looking for pointers in identifying the maximum number of 1xGig ports supported per SIP-400 on a 7600 router.
Thanks
~sultan

Hi Jerry,
Thanks for your response.
I am looking for a 'matrix' that gives me various combinations I can stick in, though you mention that each bay can support upto 2x1G or 5x1G, that is not the case.
When I try to stick in 3 nos. of 2x1G V2 SPA I get a message something like capacity exhausted/expended etc... and the SPA goes 'down'. In addition there are loads of other SIP/SPA incompatibilities... I wonder how difficult it would have been to make a single SIP capable of having ALL the available SPAs in any combination... but then this is Cisco :-)
I have also spoken to TAC, but the response was limited to 'Please check the product specifications'.
Thanks
~sultan

Similar Messages

  • SIP-400 SPA-2X1GE

    Does SPA interface (SPA-2X1GE) support DWDM SFP? What is maximum number of SPA-2x1GE in one SIP-400 module? Does OSM-4G and 7600-ES20 module support DWDM SFP. What is difference between those cards if we talk about this card as core-facing card, and which card is best solution for core-facing.

    Cisco XR 12000 Series SPA Interface Processor 10G 12000-SIP-600 support DWDM.
    SPA-2X1GE
    SPA-1XOC12-ATM
    SPA-8XCHT1/E1

  • Can we use SPA-4XOC3-POS-V2 on 7600-SIP-400

    Hi,
    We have ordered 2 x SPA-4XOC3-POS to use on 7604, we have received SPA-4XOC3-POS-V2 from our supplier.
    I know that the SPA-4XOC3-POS-V2 are for the 12000, is there a way to use them on a 7600-SIP-400??
    Any help is appreciated.
    Thank you.
    Hitch

    This SPA is not supported on SIP-400 on 7600s. You need to get a NON V2 SPA.
    Atif

  • Port Analizer Port gigabit cisco 7600 SIP-400 SPA-5X1GE-V2

    Hi,
    I have a Wan LINK  (Layer 3), so I want to check if there are retransmissions in this link.
    Do you know if there is a way that a can do SPAN on a GigabitEthernet Port on SPA-5X1GE-V2 (Cisco 7600 Platform)
    I tried but i got this error:
    R(config)#monitor session 10 source int GigabitEthernet 4/0/0
    % Interface(s) Gi4/0/0 not supported as monitor source(s) on this platform
    Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVIPSERVICESK9-M), Version 15.1(2)S, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2011 by Cisco Systems, Inc.
      4    0  4-subslot SPA Interface Processor-400  7600-SIP-400      
      5    2  Route Switch Processor 720 (Active)    RSP720-3CXL-GE
     4/0 5xGE SPA                    SPA-5X1GE-V2     
    thanks for the Help.

    Hi,
    Does anyone have any suggestions?

  • Difference between OSM-2+4GE-WAN+ and 7600-SIP-400

    hy guys,
    If I want to use one of them as uplink, which are better ?

    Depending on your current and future requirements the decision for SIP-400 or OSM-GEWAN needs to be taken.
    As they both are different product sets meant to cater to different set of business requirements.
    SIP-400
    a) Provides you with capability to aggregate different flavours of
    OC12,OC48 and other WAN and GE Interfaces as well as use them for uplink,
    b) Supports VPLS
    c) Supports MQC with conventional QOS.
    d) Supports ATM Cell Relay.
    e) Occupies 1 slot space
    OSM-GEWAN.
    a) Provides only Gigabit aggregation and uplink.
    b) Supports VPLS.
    c) Doesnt support ATM Cell Relay.
    d) Supports MQC and conventional QOS.
    e) Occupies 1 slot space,
    Above are some difference in summary.
    But if you requirement is to have only Gig aggregation and Gig uplinks then OSM
    by far is a good choice. But if you have your aggregation done, and are looking for WAN aggregation with Enchanced features like conventional QOS and VPLS, Cell Relay etc, with the option if choosing the media types for your aggregation, then SIP-400 is vis-a-vis a good choice.
    This comparision doesnt take into consideration the throughput performance of both categories vis-a-vis.
    HTH-Cheers,
    Swaroop

  • PPPoE Cisco 6500 + 7600-SIP-400

    Hello,
    we use a lot of Cisco 6500 switches across our network. I bought one 7600-SIP-400 with one SPA-5X1GE-V2 module.
    Unfortunatelly I have found that there is no command support for PPPoE in my IOS version 12.2 SXI13. 
    Can somebody tell me which IOS version do I have to use to get command support for PPPoE Server?
    Thank you.
    Milan

    "Doesn't have to be a Cisco box. "
    If you're still interested in solving this (or haven't already), you can mail me at [email protected]
    Cheers,
    Anton

  • When printing in Adobe, missing the Custom Scale option.

    Adobe Version 11.0.2
    Windows 7 64 bit.
    Doesn't matter what type of network printer I select.  When selecing to print a document, under Page Sizing & Handling, there is no "Custom Scale" option.  There is on other workstations. 
    Thank you.

    Very strange.  The only thing I can suggest is to update to 11.0.5.

  • Why no SCALE option for lightbox images?

    Need SCALE options for lightbox images!
    Must have SCALE DOWN option.
    Images must scale down to display correctly on a smaller screen.
    Currently Muse Lightbox FAILS on smaller browser screens.
    Adobe please include this feature ASAP!

    Thanks for the reply
    The problem with the Fullscreen Lightbox is that the images scale up and pixelate on a larger browser viewport.
    (To avoid this requires a very large image that makes loading slow)
    So for Fullscreen Lightbox I would like a SCALE DOWN ONLY option (requested previously). Then the images would not scale up above 100% and would float centred on larger browser viewports (FIT PROPORTIONALLY option used).
    And for the standard lightbox a scale option, as requested above, would mean the image doesn't overflow on a smaller browser viewport.
    The reason for asking for scale options is to keep images looking their best at 100%, and downscaling for smaller browser ports.

  • Why don't I see the "custom scale" option when I print?

    When printing PDF files using Adobe Reader 10.1.6 I do not have the custom scale option. Is this not available in this version?
    lagoliff

    Update it from iTunes on a computer as described at the bottom of this article; devices running an iOS version prior to 5.0 can't be updated straight from the device. Unless limited by the device's hardware, it will be updated to iOS 6.1.3.
    (81584)

  • Chart Scale Options

    Hi,
    I 'm having tough time trying to figure out scaling options for my column chart.
    I have data in series. The chart does not start from Zero value. It starts from min value to max value. It is confusing sometimes.
    Also, the chart bars vary in size as if there ia huge differnce when the difference is very slight.
    Enabling the auto-scale options did'nt do any wonders. I also tried setting manual scale to get the chart display from Zero - Max
    value and the chart compressed in size and no bars were visible.
    Is there a fix /workaround for this ?
    I want the chart to display from Zero and should have the ability to auto-scale.
    Thanks,
    Sam

    Sam,
    Yes, there is a workaround for this...
    http://xcelsiusandme.blogspot.com/2009/09/xm-sample-14-how-to-display-chart-with.html
    -Anil

  • Time-Scale option and bookmark setting possible on Creative ZEN Vision

    Does the ZEN Vision: M 60GB has a time scale option and is it possible to set bookmarks?on songs in this player like in the old CREATIVE Nomad Jukebox 3. As a musician I like this options for exercising and rehearsals.

    Theres a bookmark feature, but it needs improvment. Theres is no Time-Scaling, a feature I miss from the Zen Xtra.

  • Printing to postscript using the scale option in UNIX

    I can print to postscript without any problems but would like to scale the page down so I can fit 4 per printed page; is ths possible with the -scale option or any other option. I know this can be done within a windows environment but can this be done in UNIX at the command line.

    The problem is a few
    blocks we havent really seen yet. All these numerics and stuff outside
    the while loop, what are they exactly, or are they just a different way
    of viewing them? The stuff with the digital at INI phase, The block
    in the lower right corner of the INI phase.
    The digital block in the
    dispatcher phase we didn't really understand. 
    I am not sure what you mean here can you circle it and send me a picture so that I can explain.
    Tim
    Johnson Controls
    Holland Michigan

  • ACE default handling of the TCP Window Scale option

    Can someone tell me a reasonable explanation why the default action of the ACE is to clear the window-scale option in SYN-segments? We were long baffled why some customers (specifically the ones with larger latencies) were suffering from poor TCP transfer speeds and resets. Packet captures confirmed the fact that the ACE was clearing window-scale options, causing the advertised receive windows to be remarkably small as the scaling factors were removed.
    Isn't intermediate tampering with the window-scale option a widely known source for TCP performance problems? Window scaling is after all a widely used TCP extension. That's why I'm curious to know why such default behaviour from the ACE.
    Our problem was of course finally resolved by explicitly allowing the window-scale option using a parameter map.

    HI Timo,
    As you know if you allows the ACE to use a window scale factor that essentially increases the size of the TCP send and receive buffers. The sender specifies a window scale factor in a SYN segment that determines the send and receive window size for the duration of the connection.
    You have defined tcp-options scale allow in the parameter map but have not specified to which scale factor this should scale to.
    The TCP window scaling feature adds support for the Window Scaling option in RFC 1323. It is recommend that increasing the window size to improve TCP performance in network paths with large bandwidth, long-delay characteristics. This type of network is called a long fat network (LFN).
    But you have not configure a TCP window-scale factor which is essential for network paths with high-bandwidth, long-delay characteristics, using the "set tcp window-scale " command.
    The window scaling extension expands the definition of the TCP window to 32 bits and then uses a scale factor to carry this 32-bit value in the 16-bit window field of the TCP header.
    You can increase the window size to a maximum scale factor of 14.
    Typical applications use a scale factor of 3 when deployed in LFNs but in you case if this is a LFN you are using default which is 0.
    So here in your case you can select how much scale factor is needed to be defined from the range 0-14 , otherwise even if you have defined in the tcp-options windlow-scale allow, but as you have not define to what factor it should scale to , so it will always use the default scale factor which is 0, means no scaling at all.
    To set the TCP window-scale factor to 3, add the second command as well in your parameter map:
    host1/Admin(config-parammap-conn)# tcp-options window-scale allow        ---> Defined already
    host1/Admin(config-parammap-conn)# set tcp window-scale 3                      ----> Needed to be added else "default scale factor 0" will be taken
    You can check in the following URL at cisco docs wiki for how ACE handles Connection at Layer 4 (L4) and Layer 7 (L7):
    http://docwiki.cisco.com/wiki/Cisco_Application_Control_Engine_(ACE)_Module_Troubleshooting_Guide,_Release_A2(x)_--_Troubleshooting_Connectivity
    Here are the details of how a tcp-options scale windows works:
    The window scale extension expands the definition of the TCP
    window to 32 bits and then uses a scale factor to carry this 32- bit
    value in the 16-bit Window field of the TCP header (SEG.WND in RFC-793).
    The scale factor is carried in a new TCP option, Window Scale.
    This option is sent only in a SYN segment (a segment with the SYN bit on),
    hence the window scale is fixed in each direction when a connection is opened.
    (Another design choice would be to specify the window scale in every TCP segment.
    It would be incorrect to send a window scale option only when the scale factor changed,
    since a TCP option in an acknowledgement segment will not be delivered reliably
    (unless the ACK happens to be piggy-backed on data in the other direction).
    Fixing the scale when the connection is opened has the advantage of lower
    overhead but the disadvantage that the scale factor cannot be changed
    during the connection.) The maximum receive window, and therefore the
    scale factor, is determined by the maximum receive buffer space.
    In a typical modern implementation, this maximum buffer space is set
    by default but can be overridden by a user program before a
    TCP connection is opened. This determines the scale factor,
    and therefore no new user interface is needed for window scaling.
    Window Scale Option The three-byte Window Scale option
    may be sent in a SYN segment by a TCP.
    It has two purposes:
    (1) indicate that the TCP is prepared to do both send and receive window scaling, and
    (2) communicate a scale factor to be applied to its receive window.
    Thus, a TCP that is prepared to scale windows should send the option,
    even if its own scale factor is 1. The scale factor is limited to
    a power of two and encoded logarithmically,
    so it may be implemented by binary shift operations.
    TCP Window Scale Option (WSopt):
    Kind: 3 Length: 3 bytes
    +---------+---------+---------+
    | Kind=3 |Length=3 |shift.cnt|
    +---------+---------+---------+
    This option is an offer, not a promise; both sides must send
    Window Scale options in their SYN segments to enable window
    scaling in either direction. If window scaling is enabled,
    then the TCP that sent this option will right-shift its true
    receive-window values by 'shift.cnt' bits for transmission in
    SEG.WND. The value 'shift.cnt' may be zero (offering to scale,
    while applying a scale factor of 1 to the receive window).
    This option may be sent in an initial segment (i.e., a
    segment with the SYN bit on and the ACK bit off).
    It may also be sent in a segment, but only if a Window
    Scale op- tion was received in the initial segment.
    A Window Scale option in a segment without a SYN bit should be ignored.
    The Window field in a SYN (i.e., a or ) segment itself is never scaled.
    Using the Window Scale Option
    A model implementation of window scaling is as follows
    All windows are treated as 32-bit quantities for storage in
    the connection control block and for local calculations.
    This includes the send-window (SND.WND) and the receive- window
    (RCV.WND) values, as well as the congestion window.
    * The connection state is augmented by two window shift counts,
    Snd.Wind.Scale and Rcv.Wind.Scale, to be applied to the
    incoming and outgoing window fields, respectively.
    * If a TCP receives a segment containing a Window Scale
    option, it sends its own Window Scale option in the segment.
    * The Window Scale option is sent with shift.cnt = R, where R
    is the value that the TCP would like to use for its receive window.
    * Upon receiving a SYN segment with a Window Scale option containing
    shift.cnt = S, a TCP sets Snd.Wind.Scale to S and sets Rcv.Wind.Scale
    to R; otherwise, it sets both Snd.Wind.Scale and Rcv.Wind.Scale to zero.
    * The window field (SEG.WND) in the header of every incoming segment,
    with the exception of SYN segments, is left-shifted by Snd.Wind.Scale
    bits before updating SND.WND: SND.WND = SEG.WND << Snd.Wind.Scale
    (assuming the other conditions of RFC793 are met,
    and using the "C" notation "<<" for left-shift).
    * The window field (SEG.WND) of every outgoing segment, with the
    exception of SYN segments, is right-shifted by
    Rcv.Wind.Scale bits: SEG.WND = RCV.WND >> Rcv.Wind.Scale.
    TCP determines if a data segment is "old" or "new" by testing
    whether its sequence number is within 2**31 bytes of the left
    edge of the window, and if it is not, discarding the data as "old".
    To insure that new data is never mistakenly considered old and vice- versa,
    the left edge of the sender's window has to be at most 2**31 away
    from the right edge of the receiver's window. Similarly with the
    sender's right edge and receiver's left edge. Since the right and
    left edges of either the sender's or receiver's window differ by
    the window size, and since the sender and receiver windows can be
    out of phase by at most the window size, the above constraints imply
    that
    2 * the max window size must be less than 2**31,
    or max window < 2**30 Since the max window is 2**S
    (where S is the scaling shift count) times at most 2**16 - 1
    (the maximum unscaled window),
    the maximum window is guaranteed to be < 2*30 if S <= 14.
    Thus, the shift count must be limited to 14 (which allows windows of 2**30 = 1 Gbyte).
    If a Window Scale option is received with a shift.cnt value exceeding 14,
    the TCP should log the error but use 14 instead of the specified value.
    The scale factor applies only to the Window field as transmitted
    in the TCP header; each TCP using extended windows will maintain
    the window values locally as 32-bit numbers. For example,
    the "congestion window" computed by Slow Start and Congestion Avoidance
    is not affected by the scale factor, so window scaling will not introduce
    quantization into the congestion window.
    Hope it will resolve your issue, else get back to us for further discussion.
    Best regards,
    Sachin Garg
    Message was edited by: sachinga.hcl

  • Cannot configure service-policy on SIP-400

    I have cisco 7606 with SIP-400 on slot1 , and I try to apply service-policy output on the interface pos1/1/0, after enter the command, the system
    generate the error "queue-limit is invalid command w/o other queueing feature".
    Why I cannot apply the service-policy?

    Thanks Marcio.
    I have added failover details to the client's tnsnames file (see below), but still i get the '500 - The Network Adapter could not establish the connection' error:
    TESTDB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = lontestdb01-vip)(PORT = 1526))
    (ADDRESS = (PROTOCOL = TCP)(HOST = lontestdb02-vip)(PORT = 1526))
    (LOAD_BALANCE = TRUE)
    (FAILOVER = TRUE)
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ESTDB)
    (FAILOVER_MODE =
    (BACKUP=lontestdb02-vip)
    (TYPE=select)
    (METHOD=preconnect)
    (RETRIES=180)
    (DELAY=5)
    Bal - the output of crs_stat -t is as follows (please note the listener on node 1 is intentionally down)
    -bash-3.00$ crs_stat -t
    Name Type Target State Host
    ora....B1.inst application ONLINE ONLINE lonestdb01
    ora....B2.inst application ONLINE ONLINE lonestdb02
    ora....DB1.srv application ONLINE ONLINE lonestdb01
    ora....DB2.srv application ONLINE ONLINE lonestdb02
    ora....BOTH.cs application ONLINE ONLINE lonestdb01
    ora....DB1.srv application ONLINE ONLINE lonestdb02
    ora....LIVE.cs application ONLINE ONLINE lonestdb01
    ora....DB2.srv application ONLINE ONLINE lonestdb02
    ora....NDBY.cs application ONLINE ONLINE lonestdb02
    ora.ESTDB.db application ONLINE ONLINE lonestdb02
    ora....01.lsnr application OFFLINE OFFLINE
    ora....b01.gsd application ONLINE ONLINE lonestdb01
    ora....b01.ons application ONLINE ONLINE lonestdb01
    ora....b01.vip application ONLINE ONLINE lonestdb01
    ora....02.lsnr application ONLINE ONLINE lonestdb02
    ora....b02.gsd application ONLINE ONLINE lonestdb02
    ora....b02.ons application ONLINE ONLINE lonestdb02
    ora....b02.vip application ONLINE ONLINE lonestdb02
    Many thanks to everyone that's helped so far
    Rup

  • 7600 SIP-400 looped to same 7600

    Hi,
    We are proposing to install SIP-400's into our PE's 7600 (sup32) in order to provide egress traffic shaping and qos for our customers.
    We are proposing to connect the SIP gig interfaces back to another line card on the same device, instead of putting another switch in front of our existing PE. This saves us a switch and lets us take advantage of the port density in our current 7600 PE's (which is why we purchased them in the first place).
    We also plan to utilise the same approach to implement pwe xconnects on the SIP-400 subinterfaces. VLAN uniqueness per port is the key feature of the SIP-400 that facilitates this.
    Has anyone run a similar setup? Any experiences to share?
    I have tested in the lab and can't see any issues so far.
    Does anyone know of a more cost effective qos / shaping solution for Ethernet tails? The SIP or ES20 based solutions seem overpriced for the pretty basic functionality we are after here. Doesn't have to be a Cisco box.
    Kent.

    "Doesn't have to be a Cisco box. "
    If you're still interested in solving this (or haven't already), you can mail me at [email protected]
    Cheers,
    Anton

Maybe you are looking for