ASA5510 Suddenly does not Work, Active LED off, I can't ping to ASA5510, also can't access the CLI through the console or the ASDM through the Startup Wizard using the browser. Is this normal? how do

You must assign an IP address to the switch to gain management access over the network. You may also need to a establish a default gateway between the switch and management stations that exist on another network segment. You can statically configure a specific IP address or direct the switch to obtain an address from a Boot Protocol (BOOTP) or Dynamic Host Configuration Protocol (DHCP) server when it is powered on. Valid IP addresses consist of four decimal numbers, 0 to 255, separated by periods. Anything outside this format is not accepted by the CLI program. NOTICE: By default, the IP address is assigned to VLAN 1 through DHCP. If you select the bootp or dhcp option, IP is enabled but does not function until a BOOTP or DHCP reply has been received. Requests are broadcast periodically by the switch in an effort to learn its IP address. (BOOTP and DHCP values can include the IP address, default gateway, and subnet mask).
To display assigned IP settings using the CLI:

1. From the Privileged Exec or Normal Exec level mode, type show ip interface and press <Enter>.
   
   

The assigned IP address and subnet mask displays.

1. From the Privileged Exec mode, type show ip redirects to display the assigned gateway IP address. Press <Enter>.
   
   

The following example displays IP settings assigned by bootp or dhcp using the CLI.

Console#show ip interface

IP address and netmask: 10.1.0.1 255.255.252.0 on VLAN 1,

and address mode: User specified.

Console# show ip redirects

ip default gateway 10.1.0.254

Console#
Before you can assign a static IP address to the switch, you must obtain the following information from your network administrator:

• IP address for the switch
  
  
• Default gateway for the network
  
  
• Network mask for the network
  
  

To assign a static IP address to the switch:

1. From the Privileged Exec level global configuration mode prompt, type interface vlan 1 to access the interface-configuration mode. Press <Enter>.
   
   
2. Type ip address ip-address netmask, where ip-address is the switch IP address and netmask is the network mask for the network.
   
   
3. Type exit to return to the global configuration mode prompt. Press <Enter>.
   
   
4. To set the IP address of the default gateway for the network to which the switch belongs, type ip default-gateway gateway, where gateway is the IP address of the default gateway. Press <Enter>.
   
   
5. To save your configuration changes, type copy running-config startup-config and then press <Enter>.
   
   

NOTICE: Only one VLAN can be assigned an IP address. If you assign an address to any other VLAN, the new address overrides the original IP address. The following example shows how to set a static IP address using the CLI.

Console(config)# interface vlan 1

Console(config-if)# ip address 192.168.1.5 255.255.255.0

Console(config-if)# exit

Console(config)# ip default-gateway 192.168.1.254

Console(config)#
To configure the switch for DHCP or BOOTP:

1. From the Privileged Exec level global configuration mode prompt, type interface vlan 1 to access the interface-configuration mode. Press <Enter>.
   
   
2. At the next prompt, use one of the following commands:
   
   
   • To obtain IP settings through DHCP, type ip address dhcp
     
     
   • To obtain IP setting through BOOTP, type ip address bootp
     
     
3. Press <Enter>.
   
   
4. To save your configuration changes, type copy running-config startup-config, and then press <Enter>.

nat (inside) access-list <ACLNAME>

It sounds like you have not allowed ICMP (ping) through the firewall, and you may need to put an access list in to allow this.

are you accessing this switch from the management VLAN? I believe this switch you will need to assign it in the CLI/Menu.

connect your laptop to the asa5510 using a cross over cable

De ce nu pot Dwnloada???

Remove this line:

static (DMZ,INSIDE) 10.10.0.0 10.10.0.0 netmask 255.255.255.0

You don't need a translation going from a lower security level to a higher one. You will also need a nat line for the dmz so that pc's on the dmz will be translated outbound. The only connection that will work on the dmz is the webserver when he's sending traffic outbound with a source port of 80. Something like:

nat (DMZ) 101 10.10.0.0 255.255.255.0

Other than that, it looks like it should be working. You've got permission, a route, and a translation. Maybe "clear local-host 10.10.0.2" to get rid of any bad xlates and try again. Check debg level syslogs, run packet captures, "clear asp drop" then "show asp drop" after an attempt?

First, make sure your terminal settings are correct.  Also, make sure you are using the right cable.  Cisco provides a flat, blue console cable with every router and switch.
Cisco lists the necessary terminal settings for most of their models here: http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a008010ff7a.shtml
Power off the router and then power it back on.
If you are still not seeing any characters through your terminal application, then the router is most likely dead and will need to be replaced.

You seem to have the last resort (o.o.o.o) set to VLAN1 which is set as an inside interface.
Is VLAN1 connected to the outside router or internet backbone?
If not, change the last resort to the outside Ethernet port.

If you can't get the manament working initially I suggest the following

Setup a console connection
Type "enable" and press enter to access priveleged exec mode on the ASA
Type "config terminal" and press enter to access configuration mode
Type "configure factory-default" and press enter to load default settings.
Assign a static IP to your PC of 192.168.1.5 and try to browse to https://192.168.1.1 (PC is plugged into management interface)

You should be prompted to begin using ASDM