Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Applications > Global File System (GFS) > Issue <<  9 of 71 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 7946
Last update: 03-20-06
Issue:
How do I allow a GFS node to connect back into the Red Hat Enterprise Linux 3 GFS cluster after being fenced by a Vixel Fibre Channel switch?
Resolution:

The Vixel Fibre Channel switch accepts telnet connections from the Red Hat Enterprise Linux 3 GFS fence_vixel I/O fencing agent.

To properly isolate and prevent the failed GFS node from causing data corruption to the shared storage, fence_vixel removes the zone access of the node's port to the other ports of the storage.

Once the failed GFS node is ready to join the GFS cluster the port on the Vixel Fibre Channel needs to be enabled. This can be done by accessing the switch via telnet:

telnet ip_address 

Note: change ip_address to the switch's IP address

In Vixel's Root Menu, type the command below:

config zone config 1 2,3,4

The example above will enable communications between port 1 and ports 2,3 and 4. It will also disable communication of the said ports to the other unnamed available ports.

Consult Vixel for further details on zoning configuration.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Applications > Global File System (GFS) > Issue <<   9  of  71  >>