---
oid: "1.3.6.1.2.1.178.1.3.3.1.5"
short-description: "t11FcSpPoNaSwMembPolicyDataRole OBJECT-TYPE"
last-modified: "2021-08-31"
parent-oid: "1.3.6.1.2.1.178.1.3.3.1"
---

## OID: `1.3.6.1.2.1.178.1.3.3.1.5`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) t11FcSpPolicyMIB(178) t11FcSpPoMIBObjects(1) t11FcSpPoNonActive(3) t11FcSpPoNaSwMembTable(3) t11FcSpPoNaSwMembEntry(1) t11FcSpPoNaSwMembPolicyDataRole(5)}
```

### Description

```asn1
t11FcSpPoNaSwMembPolicyDataRole OBJECT-TYPE
SYNTAX INTEGER {
client(1),
autonomous(2),
server(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The role of the Switch in terms of which Policy data
it retains/maintains:
'client' - the Switch operates as a Client Switch.
A Client Switch maintains its own Switch Connectivity
Object and all Fabric-wide List Objects. If FC-SP
Zoning is used, a Client Switch maintains only the
subset of the Active Zone Set that it requires to
enforce the current Fabric Zoning configuration.
'autonomous' - the Switch operates as an Autonomous
Switch. An Autonomous Switch maintains its own Switch
Connectivity Object and all Fabric-wide List Objects.
This is the same as 'client' except that if FC-SP Zoning
is used, an Autonomous Switch maintains a complete copy
of the Fabric Zoning Database.
'server' - the Switch operates as a Server Switch.
A Server Switch maintains all Fabric-wide List Objects
and the Switch Connectivity Objects of each Switch in
the Fabric. If FC-SP Zoning is used, a Server Switch
maintains a complete copy of the Fabric Zoning Database."
REFERENCE
"- ANSI INCITS 426-2007, T11/Project 1570-D,
Fibre Channel - Security Protocols (FC-SP),
February 2007, section 7.1.4.1 and table 113."
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 5324](https://www.rfc-editor.org/rfc/rfc5324.html).

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.