Cisco 6500 Sup2 IOS with SLB support

Hello
A have two questions about SLB funcionality on Cisco 6500 SUP2/MSFC2
1) Is IP LAN ONLY ios support SLB ? If yes, does it have any restrictions ?
2) How heavy IOS SLB for processor ? (i mean in dispatched mode).

Are sup-bootflash: and sup-bootdisk: the same thing ?
No, they are not. sup-bootflash: is located inside but the sup-bootdisk: is located OUTSIDE and is physically accessible. If you look at the line card, you'll see a CF slot marked "Disk0:" or "Slot0". This is the sup-bootdisk:. It is also known as "disk0:". Confusing, I know.
Can I make use of the disk0 of both chassis to perform ios upgrade ?
Of course you can. I perform VSS upgrade just using one of the disk0: and push the IOS from the disk0: to the two supervisor cards.
By setting the boot path to disk0
You can too. The sup-bootflash: and the sup-bootdisk:/disk0: are the same physical format.
A word of caution: I cannot stop reiterating the importance of checking the MD5 hash value of the IOS file in the sup-bootdisk: or sup-bootflash: BEFORE rebooting the chassis for an IOS upgrade. Make sure the MD5 hash value match exactly to the MD5 hash value found in the Cisco website. Once they are match, check the boot variable string, the config-registry and you're off to the next step.

Similar Messages

6500 with SLB blade dropped the packets from HA device.

A weird behavior observed in 6500 with SLB blade. the topology is as below:
client--HA---6500 with SLB----server farm
The first Syn packet reached the 6500 with client MAC address as source MAC and can be forwarded to the server correctly. But due to HA vendor special behavior, the second Syn packet's source MAC is rewritten to HA device MAC address and this Syn is dropped by the 6500.
Is this a special feature for 6500? And is it possible to change this behavior?
Thanks in advance.

Thanks for your reply.
1, HA device is from other vendor. It works as transparent mode and the session will be processed by 2 blades in the round-robin schedule.
The first SYN is processed by the master and reach the 6500 with client MAC as the source MAC. the second SYN is processed by the slave and the source MAC is rewritten to the slave's interface mac. This SYN packet is dropped by either 6500 or CSM, not quite sure.
2, The image on the 6500 is as below:
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-PK9SV-M), Version 12.2(17d)SXB10, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Thu 11-Aug-05 14:15 by kellythw
Image text-base: 0x40020FBC, data-base: 0x41F20000
cisco WS-C6503-E (R7000) processor (revision 1.1) with 458752K/65536K bytes of memory.
Processor board ID FOX0930005J
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
3, which command should be used to "Capture a trace of the csm etherchannel"?
It seems that only the SYN with rewritten source MAC is dropped. The SYN with client MAC works fine.
Should you need any other information, pls let me know.
Thanks & Regards

Cisco 6500 with sup720 booting to rommon

Please how can I solve this problem. This cisco 6500 boots to rommon mode, I can't see any error showing why its booting to rommon.

Here is the boot process:
System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Testing lower main memory - data equals address
Testing lower main memory - checkerboard
Testing lower main memory - inverse checkerboard
Clearing lower memory for cache initialization
Clearing bss
Clearing autoboot state machine
melody_present_reg: 1st read w/ 0x5555
melody_present_reg: 2nd read w/ 0xaaaa, reversed: 0x5555
Bootdisk adapter is detected, enabling bootdisk access...
Reprogramming CS1 w/ Melody value...
Reading monitor variables from NVRAM
Reset reason for CPU board 0xffff , BaseBoard 0x281ffff, display 0x20000System Reset by Software.
Enabling interrupts
Initializing TLB
Initializing cache
Initializing required TLB entries
MOBILE dimm - rev 0.15
Initializing main memory
Sizing NVRAM
Initializing PCMCIA controller
Initializing USB2.0 controller
Exiting init
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
Autoboot: failed, BOOT string is empty
Autoboot executing command: "boot "
Initializing ATA monitor library...
string is bootdisk:s72033-ipbasek9-mz.122-33.SXJ2.bin
Loading image, please wait ...
Initializing ATA monitor library...
Stack pointer       : 0x8FFFFF80
monstack            : 0x800FFFC0
monra               : 0xBFC26EC4
edata : 0x80108580
magic : 0xFEEDFACE
memsize             : 0x10000000
uncomp_size         : 0x05090C00
comp_size           : 0x05090C00
comp_checksum       : 0x98ECBE18
uncomp_checksum     : 0x98ECBE18
CZIP_MEM_BASE       : 0x80000000
_end       : 0x8010BA00
Self extracting the image...
IOS compressed src copy is     : 0x80108594
czip + IOS tar size is :0x00E01FA8
czip + IOS Tar image is now :0x80108794
cptr is now :0x8010BB00
IOS compressed dest copy is     : 0x8010BB00
[OK]
image_entry :0x80100000
image_entry :0x80100000
__start : 0x80100000
tar_avail_size is now :0x0428EA00
Tar image address is             : 0x80F0DB00
tar_size is           : 0x0428E600
cpu type                   : 0x00000019
uncomp_size                : 0x05090C00
monstack                   : 0x800FFFC0
image_info.entry_point   = 0x80100000
image_info.section_count = 0x00000005
image_info.monstack      = 0x800FFFC0
image_info.monra         = 0xBFC26EC4
image_info.param0        = 0x00000002
image_info.param1        = 0x00000000
image_info.param2        = 0x800066A8
image_info.param3        = 0x80100000
image_info.reg_k0        = 0x80F0DB00
image_info.reg_k1        = 0x0428E600
Section Index = 0x00000000
    source    = 0x8010BC1C
    dest      = 0x80100000
    bytes     = 0x00010000
Section Index = 0x00000001
    source    = 0x8011BC1C
    dest      = 0x80110000
    bytes     = 0x00000720
Section Index = 0x00000002
    source    = 0x8011C33C
    dest      = 0x80110720
    bytes     = 0x00000020
Section Index = 0x00000003
    source    = 0x8011C35C
    dest      = 0x80110740
    bytes     = 0x00DF1730
Section Index = 0x00000004
    source    = 0x80F0DA8C
    dest      = 0x80F01E70
    bytes     = 0x00000000
reg_v0: 0x00000000
reg_k0: 0x80F0DB00
reg_k1: 0x0428E600
tar_start: 0x00000000
tar_size: 0x00000000
Tar image address is             : 0x80F0DB00
tar size is :0x00B6130E
Tar magic : ustar Tar filename : C2LC memsize             : 0x10000000
Tar gid         : 035231Tar uncomp_size         : 0x00B6130E
Tar mtime         : 11672344432 Tar username          : ccaiTar comp_checksum       : 0x0000125F
Tar group name    : buildTar prefix    : tar_size in czip         : 0x0428E600
Stack pointer       : 0x8FFFFF80
monstack            : 0x800FFFC0
monra               : 0xBFC26EC4
edata : 0x80110740
magic : 0xFEEDFACE
memsize             : 0x10000000
uncomp_size         : 0x02B3E7F0
comp_size           : 0x00DF171C
comp_checksum       : 0xE917F280
uncomp_checksum     : 0xD094D890
Compressed IOS src copy is     : 0x80110754
tar_dest is :0x8BD69200
tar_size is :0x0428E600
Compressed IOS dest copy is     : 0x8AF77AE4
Tar src before IOS decompression is     : 0x80F0DB00
Tar dest before IOS decompression is     : 0x8BD69200
compressed IOS src is     : 0x8AF77AE4
IOS uncompressed dest copy is     : 0x8013C160
Self decompressing the image : ############################################################################################################################################################################################################################## [OK]
e_shoff :
0x02B3E660
e_flags : 0x10001001
e_phnum :
0x00000001
Source elf_hdr->e_shnum = 0x0000000A
Setting up to copy ELF section 0x00000001
to image_info section 0x00000000
sh_name = 0x0000000B
sh_type = 0x00000001
sh_flags = 0x00000007
sh_addr = 0x80100000
sh_offset = 0x00000060
sh_size = 0x02640000
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000020
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000002
to image_info section 0x00000001
sh_name = 0x00000011
sh_type = 0x00000001
sh_flags = 0x00000003
sh_addr = 0x82740000
sh_offset = 0x02640060
sh_size = 0x00373440
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000008
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000003
to image_info section 0x00000002
sh_name = 0x00000017
sh_type = 0x00000001
sh_flags = 0x00000003
sh_addr = 0x82AB3440
sh_offset = 0x029B34A0
sh_size = 0x0003EEE4
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000004
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000004
to image_info section 0x00000003
sh_name = 0x00000024
sh_type = 0x00000001
sh_flags = 0x10000003
sh_addr = 0x82AF2324
sh_offset = 0x029F2384
sh_size = 0x0000423C
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000010
sh_entsize = 0x00000000
sh_type = 0x00000008
sh_flags = 0x10000003
sh_addr = 0x82AF6560
sh_offset = 0x029F65C0
sh_size = 0x00000940
sh_type = 0x00000008
sh_flags = 0x00000003
sh_addr = 0x82AF6EA0
sh_offset = 0x029F65C0
sh_size = 0x021FE100
tar file start = 0x84D02F50
cpu type                   : 0x00000019
uncomp_size                : 0x02B3E7F0
monstack                   : 0x800FFFC0
image_info.entry_point   = 0x80100000
image_info.section_count = 0x00000005
image_info.monstack      = 0x800FFFC0
image_info.monra         = 0xBFC26EC4
image_info.param0        = 0x00000002
image_info.param1        = 0x00000000
image_info.param2        = 0x800066A8
image_info.param3        = 0x80100000
image_info.reg_k0        = 0x84D02F50
image_info.reg_k1        = 0x0428E600
Section Index = 0x00000000
    source    = 0x8013C1C0
    dest      = 0x80100000
    bytes     = 0x02640000
Section Index = 0x00000001
    source    = 0x8277C1C0
    dest      = 0x8274CFB0
    bytes     = 0x00373440
Section Index = 0x00000002
    source    = 0x82AEF600
    dest      = 0x82AC03F0
    bytes     = 0x0003EEE4
Section Index = 0x00000003
    source    = 0x82B2E4E4
    dest      = 0x82AFF2D4
    bytes     = 0x0000423C
Section Index = 0x00000004
    source    = 0x8BD69200
    dest      = 0x84D02F50
    bytes     = 0x0428E600
data_size in czip         : 0x00001000
bss end of IOS is         : 0x84D01F50
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, s72033_sp Software (s72033_sp-IPBASEK9-M), Version 12.2(33)SXJ2, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 15-Dec-11 01:29 by prod_rel_team
Image text-base: 0x4010132C, data-base: 0x4274CFB0
Active crashed three times, disabling auto-boot and dropping to rommon
Firmware compiled 15-Nov-11 14:23 by integ Build [100]
*Jan 1 02:27:12.643: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch
*Jan 1 02:27:13.459: %PFREDUN-4-SUP_FORCE_TO_ROMMON: Supervisor forced to rommon with reason: Active crashed three times in a row
System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
rommon 1 >

IDSM2 on 6500-IOS inline mode support?

Hi,
I have an IDSM-2 running IPS5.1(1d) software (recently upgraded from 4.x) that is sitting on a 6500 IOS.
The IPS device manager shows gi0/7 and gi0/8 as both in Promiscuous mode. There is no option to change the mode to inline and pair them.
Is it so that IDSM-2 currently supports only Promiscuous mode?
If so, then this module is still acting as an IDS despite running IPS5.1. Isn't it? What is the advantage that I get after upgrading it from 4.x to 5.1?
-- Vasanth

There are 2 pieces to the puzzle.
There is the IDSM-2 version and what it supports, but also the Cat 6K Native IOS version and what it supports.
IDSM-2 v5.1(1d) supports
a) Promiscuous mode,
b) InLine Interface Pair mode (2 interfaces are paired for inline monitoring), and also
c) InLine Vlan Pair mode (2 vlans on a single interface are paired for inline monitoring, you will also see it called inline-on-a-stick)
But for these features to be used, the switch code must also support configuring the switch side of the IDSM-2 for each of these 3 features.
Native IOS Versions prior to 12.2(18)SXE will support only Promiscuous mode on the IDSM-2.
12.2(18)SXE and later versions will support InLine Interface Pair mode on the IDSM-2.
No Native IOS versions currently support InLine Vlan Pair mode on the IDSM-2 (a new Native IOS versions with this support is currently in development).
So to get Inline (IPS) functionality you need to be running a Native IOS version 12.2(18)SXE or later, and on the IDSM-2 run IPS versions 5.1 (or even the older 5.0).
(NOTE: Cat OS 8.5(1) does support all 3 modes of the IDSM-2. So if you are using Cat OS instead of Native IOS, then run version 8.5(1) to have access to all of the features of IPS 5.1(1) on the IDSM-2)
If you are running a Native IOS version prior to 12.2(18)SXE then the IDSM-2 can only be operated in Promiscuous mode even if 5.1(1) is loaded on the IDSM-2.
However, even in promiscuous mode the IPS 5.1(1) software does have a few advantages.
There are several engines, and engine parameters that are only supported in the 5.1 version and not the 4.0 version. So there are several signatures that are either a) not even created for 4.x sensors, or b) the 4.x signature is not as precise as the 5.x signature in the new engines.
(These new engines have proved invaluable in writing signatures to detect some of the new attacks that have come out over the past year.)
There are of course other advantages as well:
For example:
1) Risk Rating to better aid in prioritization of alerts.
2) More flexible fitlering mechanism for alerts that allows for fitlering individual actions
The 2 features above are just 2 of the new features that have been added in 5.0 and 5.1 that apply to both promiscuous and inline modes.

Cisco SSL-VPN / webvpn with Cisco 2901 IOS 15.3.3M

Dear Community,
I have a strange issue that I am hoping some of you will be able to assist with.
I am running an environment with the following specifications
Cisco ISR G2 2901 with IOS 15.3.3M
Security Licence enabled
Data Licence enabled
VPN Licence enabled
Cisco ISR G2 2951 with IOS 15.3.3M
Security Licence enabled
Data Licence enabled
SM with ESX server.
Desktop Environment
Windows XP SP3
Internet Explorer 8
Desktop Environment 2
Windows 8
Internet Explorer 10
I have a ESX server set up with a web page on the 2951. The 2901 unit has a SSL VPN / web vpn service set up on it to allow the Desktop Environments to connect to the 2951 web page. The Desktop Environments are not allowed to directly connect to the 2951 router that is why the SSL-VPN / web vpn is used.
This system was initially working with IOS 15.2.4M2 however an update of the IOS was required and now the VPN does not fully function correctly.
PROBLEM: Now the webvpn interface loads with the welcome screen and login. After logging in it has a screen with a link to the webpage on the 2951. When I try open this webpage on the 2951 and the SSL-VPN starts to build I only get half my web page. There seems to be a problem where I only get half a page loading or just a blank page with just HTML headers. I have tried changing the page to just HTML but it still does not display properly. This is with Internet Explorer ( all versions ). With firefox there are no problems but I cannot run this browser as my environment will not allow it.
If anyone can assit me here it would really make my day.
Thanks,
Will

Can anyone help with this ?

Is DOM supported using SNMP on Cisco 6500;s?

Is DOM supported using SNMP on Cisco 6500's? I've configured DOM on 6509 using transceiver type all -> monitoring. Is DOM enable for SNMP mibs? Here's the MIB I got from a vendor. .1.3.6.1.4.1.3607. And I'm unable to walk it on any of my Cisco devices including Nexus 5672 and 4900.

That oid looks like the sysoid for the ONS series of products. I don't think that will work in this case. Unfortunately, I can't offer any other advice, I've not looked into snmp support for DOM.
chris

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

Policy Based Routing is not working with slb configured

I have a 7609 with a slb firewallfarm configured. It is running IOS 12.2(18)SXE3 with sup720. The firewallfarm is configured with default settings with no access parameter, only real servers configured.
All the traffic is coming from a single vlan (it's not possible to implement another layer 2 way to make the traffic pass through) and I would like to make a single flow to exit from another interface and not pass to the real servers configured on FWfarm. I wrote the following PBR statements:
!!!!!!! Begin !!!!!!!
access-list 110 permit ip host XX.XX.XX.XX any
!where XX.XX.XX.XX is an omitted IP address
route-map NEW-ROUTEMAP permit 10
match ip address 110
set ip next-hop 192.168.253.3
interface Vlan55
!vlan 55 is the interface from where the selected flows comes
ip route-cache policy
ip policy route-map NEW-ROUTEMAP
!!!!! END !!!!!!!
The route-map seems working, in fact I can see matched ACL and route-map.
The problem is the SLB seems to take all the traffic in charge, also the one I would like to route to another interface, in fact if I put my desidered output interface in monitor I can see no traffic passing through.
SLB creates the sticky entry anyway, in fact as far as I know, the SLB has the priority to static routing and route-maps.
Any idea for a workaround? Is there a way to make PBR works with SLB?
Thanks in advance.
Ric

It's possible to make pbr work with slb for further details refere to the link ,
http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca75d.html

Do Cisco router 2811 and Catalyst 3750 support SNMPv3?

Hi,
Do Cisco router 2811, IOS 12.4(20)Ti, and Catalyst 3750, IOS 12.2.(53)SE, support SNMPv3?
Attached file contains my SNMPv3 configurations and "show snmp" results. Would you please give me your advice? Thanks.
Hugh

Hugh
Certainly both the 2811 and the 3750 do support SNMPv3. So support for the feature is not an issue in your situation.
I have looked at the config that you attached and believe that it looks reasonable. You have not told us about the SNMP server that will communicate with these devices. So we have no way to know if the details of the configuration are correct.
Have you attempted to discover these devices with an SNMP server that is configured to use SNMPv3 and has this user and passwords configured? If it does not work my first suggestion would be to check to verify that the passwords configured are exactly the same on the clients and on the server (and perhaps re-configure the passwords just to be sure). If the passwords are not a problem my second suggestion would be to check and verify that the authentication and encryption parameters match between the server and the clients.
HTH
Rick

Cisco Catalyst 4507R+E with WS-X4748 blade, ports not working

I have a Cisco Catalyst 4507R+E (with Sup7-E) and two blades; one WS-X4748-RJ45V+E and one WS-X4648-RJ45-E.
When I connect a device to a port on the WS-X4748-RJ45V+E blade the port will not come up, show interface shows the status as "notconnect". When I connect the same device to the WS-X4648-RJ45-E blade the interface comes up.
The WS-X4748-RJ45V+E blade seems to have initialised okay, it appears in the output of "show module" as OK.
I get exactly the same effect on a second, identically configured Catalyst 4507R+E.
The software version is IOS XE 3.1.0SG, which according to the release notes supports the WS-X4748-RJ45V+E blade. Has anybody else seen anything like this?

I have 2 Core switches, single SUP on each.
Line cards #1 and #2 randomly stop forwarding packets, only solution is to reload the switch ( hw-module reset does not work ). I have cat4500e-universalk9.SPA.03.05.00.E.152-1.E.bin and the sympton looks the same as the described one,
although the code is newer than 3.2.2SG.
Now we are downgrading to cat4500e-universalk9.SPA.03.04.02.SG.151-2.SG2.bin to check if that solves the issue,
otherwise we´ll try removing/re-inserting the modules, and if issue persists, most probably RMA the Core1.
We´ve sent a show tech to Cisco support while the issue was happening.
Current modules on the Core switches.
Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
1    48 10/100/1000BaseT EEE (RJ45)            WS-X4748-RJ45-E    CAT1627L48B
2    48 10/100/1000BaseT EEE (RJ45)            WS-X4748-RJ45-E    CAT1629L0ZY
3     4 Sup 7-E 10GE (SFP+), 1000BaseX (SFP)   WS-X45-SUP7-E      CAT1629L1PD
5    12 1000BaseX (SFP)                        WS-X4612-SFP-E     JAE163007EO
M MAC addresses                    Hw Fw           Sw               Status
--+--------------------------------+---+------------+----------------+---------
1 30f7.0d57.80c0 to 30f7.0d57.80ef 1.1                               Ok
2 30f7.0dac.fd40 to 30f7.0dac.fd6f 1.1                               Ok
3 30f7.0dca.6c00 to 30f7.0dca.6c03 2.1 15.0(1r)SG10 03.05.00.E       Ok
5 a493.4c44.13e8 to a493.4c44.13f3 1.1                               Ok
Mod Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+----------------------------------
3   Active Supervisor   SSO                 Active

IP TCP intercept cisco 6500

Hi,
does anyone has experience with ip tcp intercept configuration on cisco 6500 for protecting network against TCP SYN flooding.
Which mode is recommended to configure (intercept or watch) and how can affect CPU on cisco 6500?
Any infos regarding that would be much appreciated.
Thank you
Salja

Hey Salja,
In Sup720 for TCP Intercept the support is as follows:
Watch mode: Initial TCP packets (SYN, SYN-ACK and ACK of SYN-ACK) and terminating TCP packets (FIN, RST) of a TCP flow is sent to RP for processing in SW. All other TCP packets of the flow are handled in HW using netflow (if TCP packets come in before the netflow entry is created it will get punted to SW). Note that the rate of netflow entry creation is limited and if new TCP connections come in at a rate faster than the rate at which netflow entries can be created in HW there will be large number of packets hitting the CPU.
Intercept Mode: For Intercept mode without timeout the behavior is similar to Watch mode mentioned above. Intercept mode with timeout all packets of a TCP flow is handled in SW by the RP.
So its not advised to use TCP intercept on 6500 as it may degrade box performance. I would suggest using firewall for this feature.
HTH.
Regards,
RS.

Cisco 6500 power supply and module (hot-swappable?)

Hi everyone!
We have currently a Cisco 6500 with 2 power supply of 3000w. We want to replace these PS for 2 new ones, which have higher wattage: 6000w.
Can we replace them without needing to turn the 6500 off?. I mean, What happens if we insert a 6000w PS and the switch is working with one 3000w PS?
Is it possible to do this replacement "on hot"?
And second, we also have a ws-x6708-10g-3c module. Can we insert this module "on hot"? Without needing to turn the Catalyst 6500 off?
Thanks a lot! and looking forward to an answer.

Depends on your setup the table should be able to help:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/pwr_envr.html#wp1020384
Configuration Change
Effect
Redundant to nonredundant
•System log and syslog messages are generated.
•System power is increased to the combined power capability of both power supplies.
•Modules marked power-deny in the show power oper state field are brought up if there is sufficient power.
Nonredundant to redundant (both power supplies must be of equal wattage)
•System log and syslog messages are generated.
•System power is decreased to the power capability of one supply.
•If there is not enough power for all previously powered-up modules, some modules are powered down and marked as power-deny in theshow power oper state field.
Equal wattage power supply is inserted with redundancy enabled
•System log and syslog messages are generated.
•System power equals the power capability of one supply.
•No change in module status because the power capability is unchanged.
Equal wattage power supply is inserted with redundancy disabled
•System log and syslog messages are generated.
•System power is increased to the combined power capability of both power supplies.
•Modules marked power-deny in the show power oper state field are brought up if there is sufficient power.
Higher or lower wattage power supply is inserted with redundancy enabled
•System log and syslog messages are generated.
•The system does not allow you to operate a power supply of different wattage even if the wattage is higher than the installed supply. The inserted supply shuts down.
Higher or lower wattage power supply is inserted with redundancy disabled
•System log and syslog messages are generated.
•System power is increased to the combined power capability of both power supplies.
•Modules marked power-deny in the show power oper state field are brought up if there is sufficient power.
Power supply is removed with redundancy enabled
•System log and syslog messages are generated.
•No change in module status because the power capability is unchanged.
Power supply is removed with redundancy disabled
•System log and syslog messages are generated.
•System power is decreased to the power capability of one supply.
•If there is not enough power for all previously powered-up modules, some modules are powered down and marked as power-deny in theshow power oper state field.
System is booted with power supplies of different wattage installed and redundancy enabled
•System log and syslog messages are generated.
•The system does not allow you to have power supplies of different wattage installed in a redundant configuration. The lower wattage supply shuts down.
System is booted with power supplies of equal or different wattage installed and redundancy disabled
•System log and syslog messages are generated.
•System power equals the combined power capability of both power supplies.
•The system powers up as many modules as the combined capacity allows.

The three main hurdles to porting existing Flash projects to iOS with AIR

The purpose of this discussion is to identify significant problems currently preventing AIR for iOS from being a viable solution for porting existing Flash apps. These issues have been largely ignored by Adobe, so I hope that everyone will add to this discussion if you have also run into these roadblocks in targeting iOS with the AIR SDK. I hope that Adobe staff will address and provide some much needed information with regard to fixing these problems.
There are 3 main problems with targeting iOS currently, which are probably affecting anyone who is trying to port a project that is both medium to large in size and makes use of SWF loading. Pretty much any project that has a MVC architecture is going to load SWF assets that are compiled against a view class, so this is likely affecting many people.
1. Bug - ADT packager runs out of memory when packaging "large" numbers of SWF assets
https://bugbase.adobe.com/index.cfm?event=bug&id=3511656
This is a blocking bug that prevents packaging projects with a large number of SWF assets. It is preventing me from being able to package all the needed assets for my project. I provided Adobe with my project to package a couple months ago so this bug can be reproduced in house and fixed. The Adobe employee who was handling this never tried to reproduce the issue and has stopped responding to email and comments in the bug. Adobe, please have someone take charge of testing and fixing this bug. It seems like it would be a straightforward fix once the failure is reproduced within a debugger.
Has anyone who has encountered this problem determined the number of files or classes where it starts to fail. I've spent some time trying to reverse engineer what the packager is doing when it runs out of memory, so think I can determine how many classes it's working with, but obviously the size of the classes will be variable and so this number will probably be more of a range where we start to get into the failure state.
Please let me know if you can reproduce this issue with your project with many SWF assets and upvote the bug if you are already aware of this one.
2. Bug - SWF reloading when doing a "real" (AOT) compile
https://bugbase.adobe.com/index.cfm?event=bug&id=3636385
There is already a forum post that covers the history of this issue (http://forums.adobe.com/message/4920638) but that also covers some issues in older AIR builds with loading of any SWF asset (previously fixed), where this bug deals specifically with reloading of SWF assets that include compiled bytecode (ABC).
The expectation here is that all versions of the Flash runtime should handle SWF reloading with ABC in the same way, so that a single codebase can be used to target web and iOS (or any other platform). This is the only issue of the 3 that has a legitimate work around, in my opinion, because the assets can be cached within the app within a loading manager layer. All the application code that makes loading calls can stay the same, and a compiler flag can be used to enable this caching for iOS builds, with subsequent requests returning a new instance of the cached asset. This can potentially lead to a very bloated memory footprint for the running app after a period of time, though, which could make some apps perform poorly, so a bugfix is ultimately needed.
3. Unimplemented feature (?) - The constraint that a single ApplicationDomain is used when running AIR for iOS
I did ask about this in the same forum post as SWF reloading but didn't get an Adobe response. Why does this constraint exist? My guess is that the AIR runtime for iOS simply hasn't implemented multiple ApplicationDomain support at this point, and that this was done to focus resources on other high priority features for the iOS runtime. It's possible that there is some aspect of the iOS operating system that makes it difficult or impossible to implement this feature, which may be why it's been avoided to this point, but obviously this is all conjecture without hearing from Adobe on it.
This is a major issue that needs to be addressed. For us, the problem is that our SWFs for multiple instances of the same type of asset use the same name for the AS export. For example, each item an avatar can equip is a single SWF with multiple sub assets -- the parts which comprise the item. Each of the parts will have an AS export name based on the avatar facing and where it is equipped, like "fv_head". This naming is consistent across all items, so we will load a lot of assets containing "fv_head" simultaneously. This normally works fine because the default behavior for Flash has always been that each SWF is loaded into a new ApplicationDomain instance, but for iOS a single ApplicationDomain must be used, causing these names to collide. The last SWF loaded containing a given AS export name overwrites the previous ones of that name.
The work around for this, and I use that term loosely, is to go through and uniquely name every AS export in every asset where sets of assets with the same export name is used. For us that is hundreds of items with multiple exports. Maintaining unique naming across all these parts is also a very error prone process, not to mention all the code that manipulates the parts needs to be modified to handle the new naming and make sure it's referring to the now uniquely named assets.
The expectation here is that all versions of the Flash runtime should handle asset loading in the same way and place each loaded asset into its own ApplicationDomain container as the default behavior. I'd like an Adobe employee to address my assumption that this is an unimplemented feature of AIR for iOS at this point, and let the community know if a solution for this will be implemented.
Summary
All three of these issues in combination are a major roadblock to porting existing Flash games to iOS with AIR. Issues with one can make it hard to test and try to work around others. All need to be fixed, but If I could only pick one of these to fix, it would have to be issue 3 -- that lack of proper ApplicationDomain support when loading assets. This issue is completely inconsistent with standard Flash behavior and creates a major roadblock to ports of existing applications with no viable solution for a workaround.
I look forward to Adobe's feedback on each of these issues and hopefully fixes that will allow those of us working with AIR for iOS to get our products to market.

About the 3rd issue being an AoT design limitation, I'm not sure I understand why it's necessary to know during AoT packaging what the domain is that a child will be loaded into to be able to have SWF loading work as on the browser.
Isn't the ApplicationDomain an internal construct in the AIR runtime that you guys define in order to manage namespaces of loaded SWFs? To be clear, when I say "runtime" I know that the resulting code isn't being interpreted within the iOS app, but clearly you have a set of AIR libraries that get compiled into the IPA that provides support for all the Flash APIs. If that's the case, then wouldn't it be possible for the iOS version of the AIR libraries to define a new ApplicationDomain on the fly when code that has been cross-compiled to iOS native code loads a packaged SWF?
I don't have a clear picture of how ApplicationDomains are managed internal to the runtime of course, but a little more detail would be very helpful. Thanks.

What are the following:1)Cisco 1600 Series IOS WIRELESS LAN RECOVERY. 2)Service Provider Option 60 for Vendor Class Idenfier

What are the following:1)Cisco 1600 Series IOS WIRELESS LAN RECOVERY. 2)Service Provider Option 60 for Vendor Class Idenfier
These items are listed with 1600 series AP but I'm unable to understand what are these things & the use of them

DHCP Option 60: Go HERE.

IOS 7 icon support still not available in air 3.9

I am using Flash Builder 4.7 with Air 3.9 (with IOS 7 icon support) running on Win 8.
I have been battling to get a simple app on the Apple App Store because although the latest AIR 3.9 (with IOS 7 icon support) does not give an error when exporting the release build, when I try submitting my app (Using Application Loader on Mac OS X) it complains about missing icons.
When will this problem be resolved? Does anyone have an ETA?

You can edit the xml then compile with command line. But I am still having a few tweaking issues but it should work this way. But yes I hope we get a new build soon.....

Cisco 6500 Sup2 IOS with SLB support

Similar Messages

Maybe you are looking for