Sun Storage Tek 2540 M2 controller lockdown


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Sun Storage Tek 2540 M2 controller lockdown
# 1  
Old 10-18-2016
Wrench Sun Storage Tek 2540 M2 controller lockdown

hello all,

I have recently acquired the above server and i am having issues with the RAID controllers being put into a lockdown state.
This occurs when new drives are added to the array, the controller automagically reboots and then gives status codes OE and LT. After this i am unable to communicate at all with the controllers.

So far i have connected to the arrays successfully using CAM with no drives in, but when the drives are added CAM loses communication with the array/controllers.

If anyone has any experience with these arrays, is there a preferred method of installing HDD's into the array, or is there any way to remove the lockdown state from the controller?

Any help wold be greatly appreciated Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Red Hat

Sun Storage Tek 6140 compatible with RHEL5.7?

Issue Description: ================ There are of 4 servers (SunFire X440) : siman7tdw: SunFire X440 (affected server) siman8tdw:SunFire X440 (affected server) siman9tdw:SunFire X440 siman10tdw:SunFire X440 Storage Server: Sun Storage Tek 6140 (Name: simantdw_disk_bak) and Sun Storage... (1 Reply)
Discussion started by: Pawan Kumar
1 Replies

2. AIX

DS 4700 Storage Controller

We have 2 controllers in storage controller A is working, configured in Storage Controller B is not configured in Storage, but Power supply is connected for controller B. my query is, for some reason if power goes down for Controller A, wheather it will be redundant using Controllers... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. Solaris

Sun StorageTek 2540 - shutdown matrix

Hi, I have a simple question on how to correctly disable the matrix? Looking for the Common Array Manager and I do not see this option... Thank for help (3 Replies)
Discussion started by: bieszczaders
3 Replies
Login or Register to Ask a Question
FIREWALLD.LOCKDOWN(5)					   firewalld.lockdown-whitelist 				     FIREWALLD.LOCKDOWN(5)

NAME
firewalld.lockdown-whitelist - firewalld lockdown whitelist configuration file SYNOPSIS
/etc/firewalld/lockdown-whitelists.xml DESCRIPTION
The firewalld lockdown-whitelist configuration file contains the selinux contexts, commands, users and user ids that are white-listed when firewalld lockdown feature is enabled (see firewalld.conf(5) and firewall-cmd(1)). This example configuration file shows the structure of an lockdown-whitelist file: <?xml version="1.0" encoding="utf-8"?> <whitelist> <selinux context="selinuxcontext"/> <command name="commandline[*]"/> <user {name="username|id="userid"}/> </whitelist> OPTIONS
The config can contain these tags and attributes. Some of them are mandatory, others optional. whitelist The mandatory whitelist start and end tag defines the lockdown-whitelist. This tag can only be used once in a lockdown-whitelist configuration file. There are no attributes for this. selinux Is an optional empty-element tag and can be used several times to have more than one selinux contexts entries. A selinux entry has exactly one attribute: context="string" The context is the security (SELinux) context of a running application or service. To get the context of a running application use ps -e --context and search for the application that should be white-listed. Warning: If the context of an application is unconfined, then this will open access for more than the desired application. command Is an optional empty-element tag and can be used several times to have more than one command entry. A command entry has exactly one attribute: name="string" The command string is a complete command line including path and also attributes. If a command entry ends with an asterisk '*', then all command lines starting with the command will match. If the '*' is not there the absolute command inclusive arguments must match. Commands for user root and others is not always the same, the used path depends on the use of the PATH environment variable. user Is an optional empty-element tag and can be used several times to white-list more than one user. A user entry has exactly one attribute of these: name="string" The user with the name string will be white-listed. id="integer" The user with the id userid will be white-listed. SEE ALSO
firewall-applet(1), firewalld(1), firewall-cmd(1), firewall-config(1), firewalld.conf(5), firewalld.direct(5), firewalld.icmptype(5), firewalld.lockdown-whitelist(5), firewall-offline-cmd(1), firewalld.richlanguage(5), firewalld.service(5), firewalld.zone(5), firewalld.zones(5) NOTES
firewalld home page at fedorahosted.org: http://fedorahosted.org/firewalld/ More documentation with examples: http://fedoraproject.org/wiki/FirewallD AUTHORS
Thomas Woerner <twoerner@redhat.com> Developer Jiri Popelka <jpopelka@redhat.com> Developer firewalld 0.3.9 FIREWALLD.LOCKDOWN(5)