Sponsored Content
Operating Systems AIX Switch Port Becoming Private & restricting access Post 302683409 by nkiran on Wednesday 8th of August 2012 01:18:12 AM
Old 08-08-2012
Solution:

Had solved some days back, posting solution -


There is one attribute of the FC adapters called “INIT Link flags” that needs to be changed from “al” (loop) to “pt2pt” (use lsattr to figure this out). That did the trick. All my ports are now configured as F port.

procedure in short -

• Remove all scsi disks from vx & the OS first.
• Then remove all fscsi* & fcnet* devices.
• Then change the attribute (I used smitty. Devices-> FC Adapter-> FC Adapter -> Change or show attributes ... );
• Cfgmgr
• Reboot the switch & the server. (Not mandatory)

Done!
 

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
NFE(4)							   BSD Kernel Interfaces Manual 						    NFE(4)

NAME
nfe -- NVIDIA nForce MCP Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device nfe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_nfe_load="YES" DESCRIPTION
The nfe driver supports PCI Ethernet adapters based on the NVIDIA nForce Media and Communications Processors (MCP), such as the nForce, nForce 2, nForce 3, CK804, MCP04, MCP51, MCP55, MCP61, MCP65, MCP67, MCP73, MCP77 and MCP79 Ethernet controller chips. Supported features include (hardware support provided): o Receive/Transmit IP/TCP/UDP checksum offload o Hardware VLAN tag insertion/stripping o TCP segmentation offload (TSO) o MSI/MSI-X o Jumbo Frames Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The nfe driver supports the following media types: autoselect Enable autoselection of the media type and options. 10baseT/UTP Set 10Mbps operation. 100baseTX Set 100Mbps (Fast Ethernet) operation. 1000baseT Set 1000Mbps (Gigabit Ethernet) operation (recent models only). The nfe driver supports the following media options: half-duplex Force half duplex operation. full-duplex Force full duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The nfe driver supports the following NVIDIA MCP onboard adapters: o NVIDIA nForce MCP Networking Adapter o NVIDIA nForce MCP04 Networking Adapter o NVIDIA nForce 430 MCP12 Networking Adapter o NVIDIA nForce 430 MCP13 Networking Adapter o NVIDIA nForce MCP51 Networking Adapter o NVIDIA nForce MCP55 Networking Adapter o NVIDIA nForce MCP61 Networking Adapter o NVIDIA nForce MCP65 Networking Adapter o NVIDIA nForce MCP67 Networking Adapter o NVIDIA nForce MCP73 Networking Adapter o NVIDIA nForce MCP77 Networking Adapter o NVIDIA nForce MCP79 Networking Adapter o NVIDIA nForce2 MCP2 Networking Adapter o NVIDIA nForce2 400 MCP4 Networking Adapter o NVIDIA nForce2 400 MCP5 Networking Adapter o NVIDIA nForce3 MCP3 Networking Adapter o NVIDIA nForce3 250 MCP6 Networking Adapter o NVIDIA nForce3 MCP7 Networking Adapter o NVIDIA nForce4 CK804 MCP8 Networking Adapter o NVIDIA nForce4 CK804 MCP9 Networking Adapter LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.nfe.msi_disable Whether or not MSI support is enabled in the driver. The default value is 0. hw.nfe.msix_disable Whether or not MSI-X support is enabled in the driver. The default value is 0. SYSCTL VARIABLES
The following sysctl(8) variables can be used to modify or monitor nfe behavior. dev.nfe.%d.process_limit Maximum number of Rx events to be processed in the event loop before rescheduling a taskqueue. The accepted range is 50 to 255, the default value is 192. The interface does not need to be brought down and up again before a change takes effect. SEE ALSO
altq(4), arp(4), intro(4), miibus(4), netintro(4), pci(4), polling(4), rgephy(4), sysctl(8), ifconfig(8) HISTORY
The nfe device driver first appeared in OpenBSD 3.9, and then in FreeBSD 7.0. AUTHORS
The nfe driver was written by Jonathan Gray <jsg@openbsd.org> and Damien Bergamini <damien@openbsd.org>. The nfe driver was ported to FreeBSD by Shigeaki Tagashira <shigeaki@se.hiroshima-u.ac.jp>. BSD
January 15, 2011 BSD
All times are GMT -4. The time now is 10:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy