Sponsored Content
Operating Systems AIX Switch Port Becoming Private & restricting access Post 302680735 by nkiran on Thursday 2nd of August 2012 08:38:49 AM
Old 08-02-2012
Data Switch Port Becoming Private & restricting access

Hello folks,
I have an AIX server that is connected to a storage array via a Brocade switch using 4 ports from either side. The zoning is done such that there are 4 paths visible from the server to the storage.

My work involves frequent disabling or enabling the switch ports that are connected to the server. The switch ports connected to the server usually show status as "L Port Public". When I disable a port, the status for the corresponding port becomes disabled & the server starts seeing 3 paths. Everything as desired.

The issue is when I try to re-enable it. The port then shows the status as "L Port Private" & the server can not see that particular path to the storage in-spite of the port being enabled. Moreover, if I reboot the switch then all the 4 ports show status as " L Port Private"; leaving the server with zero access to the storage.

How do I make the disappeared path appear again?

This path appears again if I reboot both, the server & switch after enabling the port.
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

restricting access...

restricted access... Hi I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
Discussion started by: alwayslearningunix
9 Replies

2. UNIX for Dummies Questions & Answers

Restricting access

I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated! (4 Replies)
Discussion started by: ngagne
4 Replies

3. UNIX for Dummies Questions & Answers

Restricting access to a machine by IP Address

I have a need to allow only certain IP addresses to access a machine running solaris 9. I am not sure how this can be accomplished. Thanks in advance for your help. Patch (2 Replies)
Discussion started by: patch
2 Replies

4. Solaris

restricting access

Hi All, I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only. Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
Discussion started by: max_min
4 Replies

5. UNIX for Advanced & Expert Users

restricting root access

I'm the admin in a shop in which my developers have and use the root account, all UNIX newbies. I've been unable to convince management myself that this is an unacceptable practice. I've looked in a couple books I have and can't find any chapters, discussions, etc that make the argument that... (2 Replies)
Discussion started by: keith.m
2 Replies

6. Solaris

restricting access to a server

We want to secure access to a server by restricting the number of users who can login to it. Our users are NIS users. Only few of them can telnet/ssh this server. Do you have any idea on how to implement that? thanks. (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

7. UNIX for Advanced & Expert Users

Restricting access to code

Hi All, I am facing a problem, regarding code security on a server. We have configured a server which contains our code (ear present in jboss/server/xyz/deploy) in it, and need to bind the code to the server itself so that no one can take the code out of the. the problem is that the password of... (3 Replies)
Discussion started by: akshay61286
3 Replies

8. UNIX for Dummies Questions & Answers

Restricting SFTP access

Hello, I am using MySecureShell to chroot all sftp accesses. The problem that I have is that my boss does not want root to be able to use sftp. Root should still be able to ssh. Any ideas? (2 Replies)
Discussion started by: mojoman
2 Replies

9. Solaris

Restricting commands & access

Dear all, I am administering a DC environment of over 100+ Solaris servers used by various teams including Databases. Every user created on the node belonging to databases is assigned group staff(10) . I want that all users belonging to staff should NOT be able to execute certain system... (6 Replies)
Discussion started by: Junaid Subhani
6 Replies
fence_brocade(8)					      System Manager's Manual						  fence_brocade(8)

NAME
fence_brocade - I/O Fencing agent for Brocade FC switches SYNOPSIS
fence_brocade [OPTION]... DESCRIPTION
fence_brocade is an I/O Fencing agent which can be used with Brocade FC switches. It logs into a Brocade switch via telnet and disables a specified port. Disabling the port which a machine is connected to effectively fences that machine. Lengthy telnet connections to the switch should be avoided while a GFS cluster is running because the connection will block any necessary fencing actions. fence_brocade accepts options on the command line as well as from stdin. fenced sends parameters through stdin when it execs the agent. fence_brocade can be run by itself with command line options which is useful for testing. After a fence operation has taken place the fenced machine can no longer connect to the Brocade FC switch. When the fenced machine is ready to be brought back into the GFS cluster (after reboot) the port on the Brocade FC switch needs to be enabled. This can be done by running fence_brocade and specifying the enable action. Vendor URL: http://www.brocade.com OPTIONS
-a IPaddress IP address of the switch. -h Print out a help message describing available options, then exit. -l login Login name for the switch. -n port The port number to disable on the switch. -o action The action required. disable (default) or enable. -p password Password for login. -S path Full path to an executable to generate the password for login. -q Quiet mode: print only error messages. -V Print out a version message, then exit. STDIN PARAMETERS
agent = < param > This option is used by fence_node(8) and is ignored by fence_brocade. ipaddr = < hostname | ip > IP address or hostname of the switch. login = < param > Login name. option = < param > The action required. disable (default) or enable. passwd = < param > Password for login. passwd_script = < param > Full path to an executable to generate the password for login. port = < param > The port number to disable on the switch. SEE ALSO
fence(8), fence_node(8) fence_brocade(8)
All times are GMT -4. The time now is 05:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy