I'm having an issue with standing up a new C6509-E containing Dual SUP-2T 10G supervisor engines and both ACE30 load balancers and ASA service module (WS-SVC-ASA-SM1)
On initial boot the Sup wouldn't recognise either of these cards (it still doesn't recognise the ACE but that's another issue). After upgrading the IOS to s2t54-ipservicesk9-mz.SPA.150-1.SY1 & FDP to c6500-fpd-pkg.150-1.SY1.pkg the module is now showing as Status OK.
However, when i log onto the module using "session slot 3 processor 0" i get a prompt
SVC-APP-HW-3>, when i type en or enable i get an output "% no password set" & i am unable to login to enable mode or make any configuration changes on the module.
Cisco Website states that the enable password is blank by default, however i would expect to see a prompt which you just enter through.
There is no direct console access onto the module, so i am unable to work on the module.
I have the same issue with installation ASA service module (WS-SVC-ASA-SM1) to the new c6509-V-E with Supervisor Engine 2T. Everything as you described...
After upgrading the IOS and FPD image everything seems to look normal, the status of the module is OK, but I could not logging into the ASA-SM from the switch CLI as described in "Quick Start Guide" - "session slot 3 processor 1":
How do you describe, I was able to get into "SVC-APP-HW-3>" by "session slot 3 processor 0" and even (how to write
Jennifer Halim) into "SVC-APP-HW-3#" by "attach 3"...
But that's not what I expected, it is not ASA-SM CLI...
So by reading "Cisco ASA Services Module CLI Configuration Guide" found second connection methods - virtual console connection - using the "service-module session slot 3" ... Yes, it worked, I see now something that i wanted to see:
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...