Registered state change notification

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Registered state change notification" – news · newspapers · books · scholar · JSTOR (October 2009) (Learn how and when to remove this template message)

In

Implementation of this function is obligatory for each Fibre Channel switch, but is optional for a node. This function belongs to a second level of the protocol, or FC2.

Some events that trigger notifications are:

• Nodes joining or leaving the fabric (most common usage)
• Switches joining or leaving the fabric
• Changing the switch name

The nodes wishing to be notified in such way need to register themselves first at the Fabric Controller, which is a standardized FC virtual address present at each switch.

RSCN and zoning

If a fabric has some zones configured for additional security, notifications do not cross zone boundaries if not needed. Simply, there is no need to notify a node about a change that it cannot see anyway (because it happened in a separate zone).

Example

For example, let's assume there is a fabric with just one node, namely a server's FC-compatible

See also

• Storage area network
• Fibre Channel
  • Fibre Channel fabric
  • Fibre Channel switch
  • Fibre Channel zoning

External links

• DeSanti; et al. (August 2007). "RFC 4983: Fibre Channel Registered State Change Notification (RSCN) MIB". IETF.
  doi:10.17487/RFC4983. Retrieved 2011-06-14. {{cite journal}}: Cite journal requires |journal= (help
  )