Here are a list of frequently asked questions:

1.  How to get physical switch WWN?
2.  How to get vsan WWN?
3.  How to talk to the neighbouring switch?
4.  How do I find out how many ports a switch has? 
5.  How to figure port type?
6.  What is admin mode, and oper mode for each port? 
7.  What about port speed (fcIfAdminSpeed gives me 'auto')?
8.  Why are there strange characters in the output, and what do the multiple instances of the oids mean?
9.  How do I get the (3 byte) port Id (FCID)?
10. To figure out if a switch is a master switch, do I compare its wwn with the principal switch wwn?
11. SNMPv1 support : Switch doesn't seem to be responding to SNMPv1 requests.
12. How to get the model number of the switch using SNMP?
13. How to calculate Port Utilization?
14. Launch DM & FM
15. Are traps ver 1 or ver 2?
16. Can we modify port to receive Traps on? If so, how?
17. How to get flow statistics?
18. What is IFIndex?  How to decode IFIndex?
19. Software version number?
20. How do find Up VSANS for an ISL link?
21. How to get Switch Serial #?
22. How to download Switch Configuration File?
23. How to identify what card is "plugged" in a "slot"?
24. How to show licence host id?
25. How to determine port type (E, TE, SD...)?
26. How to identify the active zoneset? 
27. How to get "interface description field" (CLI: Show interface description)?
28. How to find interface (slot / port) of the other end of an ISL?


**********************************************************************************
1. How to get physical switch WWN?

Mib: Cisco-FC-FE-MIB

cffFcFeElementName: (part of cffFcFeConfig)

The World-Wide Name of this fabric element. It's a 64-bit identifier and is
unique worldwide.

**********************************************************************************

2.  How to get vsan WWN?

Mib: CISCO-DM-MIB

dmConfiguration.dmTable.dmEntry.dmLocalSwitchWwn


**********************************************************************************

How to talk to the neighbouring switch?

As part of the FCS mib, fcsieTable,

fcsIeMgmtAddrListIndex: "The index of the management address list
                 corresponding to this Interconnect Element. This
                 object is an index into the fcsMgmtAddrListTable.
                 Zero or more of the management address objects may
                 be associated with an Interconnect Element object."



Using the fcsIeMgmtAddrListIndex, get the management address from
fcsMgmtAddrListTable:


fcsMgmtAddrListTable:

                "This table contains the set of management
                 address lists currently referenced by any
                 instance of the fcsIeMgmtAddrListIndex or
                 fcsPlatformMgmtAddrListIndex objects."

fcsMgmtAddr

                "The management address corresponding to this entry.
                 The format of this object may be based on the
                 format of the Uniform Resource Locator (URL).
                 For example, SNMP - snmp://ipaddress[:port#].

                 This object MUST be set to a valid value before or
                 concurrently with setting the value of the
                 corresponding instance of fcsMgmtAddrRowStatus to
                 'active'."
        REFERENCE
                "ANSI NCITS xxx-200x, Fibre Channel - Generic
                 Services 3 (FC-GS-3) T11/Project 1356D/Rev 7.01
                 Section 6.1.2.1.7"


Example:

for VSAN 1 on my local switch fcsIeMgmtAddrListIndex returns:

fcsIeMgmtAddrListIndex.1.32.1.0.11.95.163.200.129:-->22
fcsIeMgmtAddrListIndex.1.32.1.0.11.190.87.108.129:-->17
fcsIeMgmtAddrListIndex.1.32.1.0.11.190.87.109.1:-->19
fcsIeMgmtAddrListIndex.1.32.1.0.11.190.87.109.65:-->18

for vsan 2:

fcsIeMgmtAddrListIndex.2.32.2.0.11.95.163.200.129:-->23
fcsIeMgmtAddrListIndex.2.32.2.0.11.190.87.108.129:-->21

Looking at partial dump of the fcsMgmtAddr (marked items associated to vsan
1 and vsan 2) :

fcsMgmtAddr.16.2:http://172.22.54.103/eth-ip
fcsMgmtAddr.17.1:snmp://172.22.54.105/eth-ip <- vsan 1
fcsMgmtAddr.17.2:http://172.22.54.105/eth-ip <- vsan 1
fcsMgmtAddr.18.1:snmp://172.22.54.103/eth-ip
fcsMgmtAddr.18.2:http://172.22.54.103/eth-ip <- vsan 1
fcsMgmtAddr.19.1:snmp://172.22.54.104/eth-ip <- vsan 1
fcsMgmtAddr.19.2:http://172.22.54.104/eth-ip <- vsan 1
fcsMgmtAddr.20.1:snmp://172.22.54.105/eth-ip
fcsMgmtAddr.20.2:http://172.22.54.105/eth-ip
fcsMgmtAddr.21.1:snmp://172.22.54.105/eth-ip <- vsan 2
fcsMgmtAddr.21.2:http://172.22.54.105/eth-ip <- vsan 2
fcsMgmtAddr.22.1:snmp://172.22.54.106/eth-ip <- vsan 1
fcsMgmtAddr.22.2:http://172.22.54.106/eth-ip <- vsan 1
fcsMgmtAddr.23.1:snmp://172.22.54.106/eth-ip <- vsan 2
fcsMgmtAddr.23.2:http://172.22.54.106/eth-ip <- vsan 2
fcsMgmtAddr.24.1:snmp://172.22.54.106/eth-ip
fcsMgmtAddr.24.2:http://172.22.54.106/eth-ip

This is how you get the management address of the switch to which you are
connected to.


**********************************************************************************

4.  How do I find out how many ports a switch has? 

RFC 2863, IF MIB is implemented

Each port has an entry in ifTable.  

To determine port type (management port, FC, ISCSI, FCIP...), refer to the 
first 8 bits of ifIndex.

**********************************************************************************

5.  How to figure port type?


ifType is an entry in the ifTable. The type of interface.  


    fibreChannel(56),   -- Fibre Channel
    gigabitEthernet(117)-- Gigabit Ethernet

So, all ports with ifType = 56 are FC ports
**********************************************************************************

6.  What is admin mode, and oper mode for each port? 


Admin Status:

 The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to
  either the up(1) or testing(3) states (or remains in the down(2) state). 

Oper Status:

The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components. 

*********************************************************************************

7.  What about port speed (fcIfAdminSpeed gives me 'auto')?

When set to auto, the port will auto negotiate the speed to either 1G or 2G when a Node logs into the port.

**********************************************************************************

8.  Why are there strange characters in the output, and what do the multiple instances of the oids mean?

I am not sure what MIB browser you are using, but the hex values seem to be right.  In fcsIeFabricName, Ie stands for interconnect element.  You are seeing multiple rows because you have multipe inerconnect elements on your switch.

**********************************************************************************
9.  How do I get the (3 byte) port Id (FCID)?

FC-FE MIB - fcIfFLoginTable - fcIfNxPortAddress gives the 3 byte fcId value.

**********************************************************************************
10. To figure out if a switch is a master switch, do I compare its wwn with the principal switch wwn?

FYI, As we have concept of VSAN, each vsan will have a principal switch.  
This information can be retrieved from the DM MIB - DM Table - dmPrincipalSwitch


**********************************************************************************
11.  SNMPv1 support : Switch doesn't seem to be responding to SNMPv1 requests.

Only community strings added thru cli can communicate using snmp v1.  
Community strings created using Device Manager support V2C and V3 only.  

**********************************************************************************
12. How to get the model number of the switch using SNMP?

>From the Entity-MIB, entyPhysicalTable, entPhysicalModelName gives the model name

**********************************************************************************

13. How to calculate Port Utilization?

To Calculate Utilization, you need atleast two gets of inOctets, outOctets, time difference between the two gets and the port speed (1/2 Gig)


1.  Calculate what the theoretical limit of traffic that could flow over the period of time
2.  To be on safe side, make sure the difference inoctets/outoctets is not greater than theoretical limit and also not negative

3.  rxUtil = (int) (inDiff / speed * 100.0) should give the utilization percentage.

**********************************************************************************
14.  Launch DM & FM

Device Manager:

cmd /c start javaw.exe  -cp bitmaps.jar;dm.jar;dmdb.jar;dmhelp.jar;jchart.jar;jh.jar;jnm.jar;snmp.jar;agent.jar -Xms6m com.andiamo.dm.DM

Fabric Manager:

cmd /c start javaw.exe  -cp bitmaps.jar;sm.jar;dm.jar;dmdb.jar;dmhelp.jar;esper.jar;layout.jar;jchart.jar;jh.jar;jnm.jar;sanmgr-topo.jar;snmp.jar;agent.jar -Xms6m com.andiamo.sm.SM


**********************************************************************************
15. Are traps ver 1 or ver 2?

MDS is capable of sending v1 or v2 traps based on how you register with MDS to receive traps.

**********************************************************************************

16. Can we modify port to receive Traps on? If so, how?

Yes, the port to receive traps on can be customized using the SNMP-Target-MIB (RFC 2573).  

snmpTargetAddrTAddress.49.55.49.46.55.49.46.52.57.46.50.49.53.47.50.48.48.51=ab:47:31:d7:07:d3, 
snmpTargetAddrParams.49.55.49.46.55.49.46.52.57.46.50.49.53.47.50.48.48.51=v2c, 
snmpTargetAddrTagList.49.55.49.46.55.49.46.52.57.46.50.49.53.47.50.48.48.51=trap, 

....

fyi...the last two bytes of snmpTargetAddrTAddress represent the port number.  The first four bytes, ip address.

**********************************************************************************
17. How to get flow statistics?

CISCO-FC-ROUTE-MIB

fcRouteFlowStatTable

fcRouteFlowType


**********************************************************************************
18. What is IFIndex?  How to decode IFIndex?

IFIndex is widely used by MDS.  IFIndex is a standard way to provide type / slot / port / subinterface in a single integer.

IFIndex is 32 bits wide:

32 bits are: 

Type: 8 bits
Slot: 5 bits
Port: 7 bits
SubInterface: 12 bits

Defined Types:

FC_TYPE = 0x01;			//Fibre Channel
ETH_TYPE = 0x02;		//Ethernet  -- 0000 0010 
PCHANNEL_TYPE = 0x04;	//Port Channel 
MGMT_TYPE = 0x05;		//Management Port (ethernet) -- 0000 0101 
INBAND_TYPE = 0x06;
VSAN_TYPE = 0x08;		//Refers to VSAN IP interface.  Used for IP-FC (RFC 2625).  
The five bits for slot are all 1 (value 31) and that is referring to the Supervisor.  
This is a virtual interface.  Nothing to do with the physical ports.
 
FCIP_TYPE = 0x0A;  -- 0000 1010 
ISCSI_TYPE = 0x0B; -- 0000 1011 
AVANTI_TYPE = 0x0C;		//related to virtualization
FV_TYPE = 0x0E;			//related to virtualization

decode code sample:
int type = ((ifIndex >> 24) & 255);
int card = ((ifIndex >> 19) & 31) + 1;
int port = ((ifIndex >> 12) & 127) + 1;
int subInterface = (ifIndex & 4095) + 1;

Sub Interface Usage:

Each Port Channel is given an id to differentiate between multiple port channels on a single switch.  
The port channel id is embedded as a sub interface.


                 

**********************************************************************************

19. Software version number?

ENTITY-MIB:

entityPhysical.entPhysicalTable.entPhysicalEntry.entPhysicalSoftwareRev

How to identify the row:  Look for entPhysicalDescr to matach "Supervisor"

**********************************************************************************

20. How do find Up VSANS for an ISL link?

Cisco FC FCE Mib provides this information.

fcIfActiveVsanUpList2k

**********************************************************************************
21. How to get Switch Serial #

Use the ENTITY mib.  entPhysicalTable has entPhysicalSerialNum.

**********************************************************************************
22. How to download Switch Configuration File?

Use the CISCO-CONFIG-COPY-MIB to do this.

**********************************************************************************
23. How to identify what card is "plugged" in a "slot"?

Entity-Mib defines PhysicalClass as below:


PhysicalClass ::= TEXTUAL-CONVENTION
    STATUS          current
    DESCRIPTION
            "An enumerated value which provides an indication of the
            general hardware type of a particular physical entity.
            There are no restrictions as to the number of
            entPhysicalEntries of each entPhysicalClass, which must be
            instantiated by an agent.

            The enumeration 'other' is applicable if the physical entity
            class is known, but does not match any of the supported
            values.

            The enumeration 'unknown' is applicable if the physical
            entity class is unknown to the agent.

            The enumeration 'chassis' is applicable if the physical
            entity class is an overall container for networking
            equipment.  Any class of physical entity except a stack may
            be contained within a chassis, and a chassis may only be
            contained within a stack.

            The enumeration 'backplane' is applicable if the physical
            entity class is some sort of device for aggregating and
            forwarding networking traffic, such as a shared backplane in
            a modular ethernet switch.  Note that an agent may model a
            backplane as a single physical entity, which is actually
            implemented as multiple discrete physical components (within
            a chassis or stack).

            The enumeration 'container' is applicable if the physical
            entity class is capable of containing one or more removable
            physical entities, possibly of different types. For example,
            each (empty or full) slot in a chassis will be modeled as a
            container. Note that all removable physical entities should
            be modeled within a container entity, such as field-
            replaceable modules, fans, or power supplies.  Note that all
            known containers should be modeled by the agent, including
            empty containers.

            The enumeration 'powerSupply' is applicable if the physical
            entity class is a power-supplying component.

            The enumeration 'fan' is applicable if the physical entity
            class is a fan or other heat-reduction component.

            The enumeration 'sensor' is applicable if the physical
            entity class is some sort of sensor, such as a temperature
            sensor within a router chassis.

            The enumeration 'module' is applicable if the physical
            entity class is some sort of self-contained sub-system.  If
            it is removable, then it should be modeled within a
            container entity, otherwise it should be modeled directly
            within another physical entity (e.g., a chassis or another
            module).

            The enumeration 'port' is applicable if the physical entity
            class is some sort of networking port, capable of receiving
            and/or transmitting networking traffic.

            The enumeration 'stack' is applicable if the physical entity
            class is some sort of super-container (possibly virtual),
            intended to group together multiple chassis entities.  A
            stack may be realized by a 'virtual' cable, a real
            interconnect cable, attached to multiple chassis, or may in
            fact be comprised of multiple interconnect cables. A stack
            should not be modeled within any other physical entities,
            but a stack may be contained within another stack.  Only
            chassis entities should be contained within a stack."
    SYNTAX      INTEGER  {
        other(1),
        unknown(2),
        chassis(3),
        backplane(4),
       container(5),     -- e.g., chassis slot or daughter-card holder
        powerSupply(6),
        fan(7),
        sensor(8),
       module(9),        -- e.g., plug-in card or daughter-card
       port(10),
       stack(11)         -- e.g., stack of multiple chassis entities
    }


entPhysicalClass is of type PhysicalClass.


Here is an partial output of "enPhysicalClass":

entPhysicalClass.1:-->chassis(3)
entPhysicalClass.2:-->container(5)
entPhysicalClass.3:-->container(5)
entPhysicalClass.4:-->container(5)
entPhysicalClass.5:-->container(5)
entPhysicalClass.6:-->container(5)
entPhysicalClass.7:-->container(5)
entPhysicalClass.8:-->container(5)
entPhysicalClass.9:-->container(5)
entPhysicalClass.10:-->container(5)
entPhysicalClass.18:-->container(5)
entPhysicalClass.19:-->container(5)
entPhysicalClass.20:-->container(5)
entPhysicalClass.21:-->backplane(4)
entPhysicalClass.22:-->module(9)	<---- //module stands for plug-in card as defined by PhysicalClass, slot 1
entPhysicalClass.23:-->module(9)	<---- //module stands for plug-in card as defined by PhysicalClass, slot 2
					<---- //Notice that empty slots are skipped
entPhysicalClass.26:-->module(9)	<---- //module stands for plug-in card as defined by PhysicalClass, slot 5
entPhysicalClass.27:-->module(9)	<---- //module stands for plug-in card as defined by PhysicalClass, slot 6
entPhysicalClass.38:-->powerSupply(6)
entPhysicalClass.40:-->fan(7)
entPhysicalClass.41:-->other(1)
entPhysicalClass.57:-->other(1)
entPhysicalClass.105:-->other(1)
entPhysicalClass.121:-->other(1)
entPhysicalClass.361:-->port(10)
entPhysicalClass.362:-->port(10)
entPhysicalClass.363:-->port(10)
entPhysicalClass.364:-->port(10)
entPhysicalClass.365:-->port(10)
entPhysicalClass.366:-->port(10)
entPhysicalClass.367:-->port(10)
entPhysicalClass.368:-->port(10)
entPhysicalClass.369:-->port(10)
entPhysicalClass.370:-->port(10)
entPhysicalClass.371:-->port(10)
entPhysicalClass.372:-->port(10)
entPhysicalClass.373:-->port(10)
entPhysicalClass.374:-->port(10)
entPhysicalClass.375:-->port(10)
entPhysicalClass.376:-->port(10)



Here is a partial output for "entPhysicalContainedIn"

entPhysicalContainedIn.1:-->0	<-- overall switch container
entPhysicalContainedIn.2:-->1	<-- "2 is member of 1" (read as, slot in a switch that can take a module)
entPhysicalContainedIn.3:-->1
entPhysicalContainedIn.4:-->1
entPhysicalContainedIn.5:-->1
entPhysicalContainedIn.6:-->1
entPhysicalContainedIn.7:-->1
entPhysicalContainedIn.8:-->1
entPhysicalContainedIn.9:-->1
entPhysicalContainedIn.10:-->1
entPhysicalContainedIn.18:-->1
entPhysicalContainedIn.19:-->1
entPhysicalContainedIn.20:-->1
entPhysicalContainedIn.21:-->1
entPhysicalContainedIn.22:-->2	<-- "22 is member of 2", remember we defined 2 as member of 1 , if you go back to entPhysicalCalss, "entPhysicalClass.22" is referred to as module.
entPhysicalContainedIn.23:-->3
entPhysicalContainedIn.26:-->6
entPhysicalContainedIn.27:-->7
entPhysicalContainedIn.38:-->18
entPhysicalContainedIn.40:-->20
entPhysicalContainedIn.41:-->22
entPhysicalContainedIn.57:-->23
entPhysicalContainedIn.105:-->26
entPhysicalContainedIn.121:-->27
entPhysicalContainedIn.361:-->22	<-- this contains in the module (port on the module)
entPhysicalContainedIn.362:-->22
entPhysicalContainedIn.363:-->22
entPhysicalContainedIn.364:-->22
entPhysicalContainedIn.365:-->22
entPhysicalContainedIn.366:-->22
entPhysicalContainedIn.367:-->22
entPhysicalContainedIn.368:-->22
entPhysicalContainedIn.369:-->22
entPhysicalContainedIn.370:-->22
entPhysicalContainedIn.371:-->22
entPhysicalContainedIn.372:-->22
entPhysicalContainedIn.373:-->22
entPhysicalContainedIn.374:-->22
entPhysicalContainedIn.375:-->22
entPhysicalContainedIn.376:-->22


entPhysicalDescr.1:-->MDS 9 Slot Chassis
entPhysicalDescr.2:-->LinecardSlot-1
entPhysicalDescr.3:-->LinecardSlot-2
entPhysicalDescr.4:-->LinecardSlot-3
entPhysicalDescr.5:-->LinecardSlot-4
entPhysicalDescr.6:-->SupSlot-5
entPhysicalDescr.7:-->SupSlot-6
entPhysicalDescr.8:-->LinecardSlot-7
entPhysicalDescr.9:-->LinecardSlot-8
entPhysicalDescr.10:-->LinecardSlot-9
entPhysicalDescr.18:-->PowerSupplyBay-1
entPhysicalDescr.19:-->PowerSupplyBay-2
entPhysicalDescr.20:-->FanBay-1
entPhysicalDescr.21:-->Backplane
entPhysicalDescr.22:-->1/2 Gbps FC Module		<-- description of the module in the slot 1
entPhysicalDescr.23:-->1/2 Gbps FC Module		<-- description of the module in the slot 2
entPhysicalDescr.26:-->Supervisor/Fabric-1		<-- description of the module in the slot 5
entPhysicalDescr.27:-->Supervisor/Fabric-1		<-- description of the module in the slot 6
entPhysicalDescr.38:-->1153.32W 110v AC
entPhysicalDescr.40:-->Fan Module
entPhysicalDescr.41:-->module-1 processor-1
entPhysicalDescr.57:-->module-2 processor-1
entPhysicalDescr.105:-->module-5 processor-1
entPhysicalDescr.121:-->module-6 processor-1
entPhysicalDescr.361:-->Linecard-1 Port-1
entPhysicalDescr.362:-->Linecard-1 Port-2
entPhysicalDescr.363:-->Linecard-1 Port-3
entPhysicalDescr.364:-->Linecard-1 Port-4
entPhysicalDescr.365:-->Linecard-1 Port-5
entPhysicalDescr.366:-->Linecard-1 Port-6
entPhysicalDescr.367:-->Linecard-1 Port-7
entPhysicalDescr.368:-->Linecard-1 Port-8
entPhysicalDescr.369:-->Linecard-1 Port-9
entPhysicalDescr.370:-->Linecard-1 Port-10
entPhysicalDescr.371:-->Linecard-1 Port-11
entPhysicalDescr.372:-->Linecard-1 Port-12
entPhysicalDescr.373:-->Linecard-1 Port-13
entPhysicalDescr.374:-->Linecard-1 Port-14
entPhysicalDescr.375:-->Linecard-1 Port-15
entPhysicalDescr.376:-->Linecard-1 Port-16


You might also be intersted in releative position (like ports):

entPhysicalParentRelPos.361:-->1
entPhysicalParentRelPos.362:-->2
entPhysicalParentRelPos.363:-->3
entPhysicalParentRelPos.364:-->4
entPhysicalParentRelPos.365:-->5
entPhysicalParentRelPos.366:-->6
entPhysicalParentRelPos.367:-->7
entPhysicalParentRelPos.368:-->8
entPhysicalParentRelPos.369:-->9
entPhysicalParentRelPos.370:-->10
entPhysicalParentRelPos.371:-->11
entPhysicalParentRelPos.372:-->12
entPhysicalParentRelPos.373:-->13
entPhysicalParentRelPos.374:-->14
entPhysicalParentRelPos.375:-->15
entPhysicalParentRelPos.376:-->16

**********************************************************************************
How to show licence host id?

switch# show license host-id
License hostid: VDH=FOX073003WQ

**********************************************************************************

25.  How to determine port type (E, TE, SD...)?

Mib: CISCO-FCS-MIB

ciscoFcsMIB.ciscoFcsMIBObjects.fcsConfiguration.fcsPortTable.fcsPortEntry.fcsPortType


CISCO-ST-TC-MIB defines fcsPortType as:

FcPortTypes ::= TEXTUAL-CONVENTION
        STATUS        current
        DESCRIPTION
               "Represents fibre channel port types:
                auto (1)   - Mode is determined by port initialization 
                            scheme.
                fPort (2)  - Fibre channel fabric port. 
                flPort (3) - Fibre channel arbitrated loop port.
                ePort (4)  - Fabric Expansion port.
                bPort (5)  - Bridging port.
                fxPort (6) - This port can only be f_port or fl_port.
                sdPort (7) - SPAN destination port. SD_ports transmit 
                            traffic copied from one or more source ports
                            for monitoring purposes.        
                tlPort (8) - Translation loop port.
                nPort (9)   - Fibre channel N port.
                nlPort (10) - Fibre channel NL port.
                nxPort (11) - This port can only be n_port or nl_port.

                  -- read only port types.
                tePort (12) - Trunking e_port.
                             Note: A port which is administratively set
                             to 'ePort', will operationally have type
                             'tePort' if fcIfOperTrunkMode has the value
                             'trunk'.
                fvPort (13) - Virtual Port.
                portOperDown (14) - port operationally down
                                    If a port is operationally down, the
                                    port mode is unknown. In such cases
                                    the operational port mode is shown 
                                    as 'portOperDown'. 
                stPort (15) - SPAN Tunnel destination port."
        SYNTAX        INTEGER {
                       auto (1),
                       fPort (2),
                       flPort (3),
                       ePort (4),
                       bPort (5),
                       fxPort (6),
                       sdPort (7),
                       tlPort (8),
                       nPort (9),
                       nlPort (10),
                       nxPort (11),
                       tePort (12),
                       fvPort (13),
                       portOperDown (14),
                       stPort (15)
                   }


FcPortTypes ::= TEXTUAL-CONVENTION
        STATUS        current
        DESCRIPTION
               "Represents fibre channel port types:
                auto (1)   - Mode is determined by port initialization 
                            scheme.
                fPort (2)  - Fibre channel fabric port. 
                flPort (3) - Fibre channel arbitrated loop port.
                ePort (4)  - Fabric Expansion port.
                bPort (5)  - Bridging port.
                fxPort (6) - This port can only be f_port or fl_port.
                sdPort (7) - SPAN destination port. SD_ports transmit 
                            traffic copied from one or more source ports
                            for monitoring purposes.        
                tlPort (8) - Translation loop port.
                nPort (9)   - Fibre channel N port.
                nlPort (10) - Fibre channel NL port.
                nxPort (11) - This port can only be n_port or nl_port.

                  -- read only port types.
                tePort (12) - Trunking e_port.
                             Note: A port which is administratively set
                             to 'ePort', will operationally have type
                             'tePort' if fcIfOperTrunkMode has the value
                             'trunk'.
                fvPort (13) - Virtual Port.
                portOperDown (14) - port operationally down
                                    If a port is operationally down, the
                                    port mode is unknown. In such cases
                                    the operational port mode is shown 
                                    as 'portOperDown'. 
                stPort (15) - SPAN Tunnel destination port."
        SYNTAX        INTEGER {
                       auto (1),
                       fPort (2),
                       flPort (3),
                       ePort (4),
                       bPort (5),
                       fxPort (6),
                       sdPort (7),
                       tlPort (8),
                       nPort (9),
                       nlPort (10),
                       nxPort (11),
                       tePort (12),
                       fvPort (13),
                       portOperDown (14),
                       stPort (15)
                   }


**********************************************************************************
26. How to identify the active zoneset?

ciscoZsMIB.ciscoZoningMIBObjects.zoneConfiguration.zoneEnforcedZoneSetTable

zoneEnforcedZoneSetTable has zoneEnforcedZoneSetName.  As zone set names with in a VSAN are unique, string comparision of zoneset names will identify the active zone set.  FYI...if this table has no entries for a VSAN, no active zoneset is present for that VSAN. 

**********************************************************************************
27. How to get "interface description field" (CLI: Show interface description)?

ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifAlias  has the interface description information.

**********************************************************************************

28. How to find interface (slot / port) of the other end of an ISL?

FROM fcsConfiguration.fcsPortTable.fcsPortEntry.fcsPortAttachPortNameIndex

fcsPortAttachPortNameIndex.1.32.1.0.5.48.1.18.130:-->3  <-- use this to get the fcs Attach Port Name (you can get more than one, in case of a JBOD) fcsPortAttachPortNameIndex.1.32.2.0.5.48.1.18.130:-->0

fcsPortAttachPortNameIndex.1.32.3.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.4.0.5.48.1.18.130:-->0

fcsPortAttachPortNameIndex.1.32.5.0.5.48.1.18.130:-->2  <-- use this to get the fcs Attach Port Name (you can get more than one, in case of a JBOD) fcsPortAttachPortNameIndex.1.32.6.0.5.48.1.18.130:-->0

fcsPortAttachPortNameIndex.1.32.7.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.8.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.9.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.10.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.11.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.12.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.14.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.15.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.16.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.17.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.18.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.19.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.20.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.21.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.22.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.23.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.24.0.5.48.1.18.130:-->0

fcsPortAttachPortNameIndex.1.32.25.0.5.48.1.18.130:-->1  <-- use this to get the fcs Attach Port Name (you can get more than one, in case of a JBOD) fcsPortAttachPortNameIndex.1.32.26.0.5.48.1.18.130:-->0

fcsPortAttachPortNameIndex.1.32.27.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.28.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.29.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.30.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.31.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.32.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.33.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.34.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.35.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.36.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.37.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.38.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.39.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.1.32.40.0.5.48.1.18.130:-->0
fcsPortAttachPortNameIndex.4094.32.13.0.5.48.1.18.130:-->0



fcsPortPhyPortNum.1.32.1.0.5.48.1.18.130:-->16777216 <-- provides the switch port if index 16777216 breaks down to fc 1/25

This is configured as a TE port

fcsPortPhyPortNum.1.32.2.0.5.48.1.18.130:-->16781312
fcsPortPhyPortNum.1.32.3.0.5.48.1.18.130:-->16785408
fcsPortPhyPortNum.1.32.4.0.5.48.1.18.130:-->16789504

fcsPortPhyPortNum.1.32.5.0.5.48.1.18.130:-->16793600 <-- attach index 2
fcsPortPhyPortNum.1.32.6.0.5.48.1.18.130:-->16797696
fcsPortPhyPortNum.1.32.7.0.5.48.1.18.130:-->16801792
fcsPortPhyPortNum.1.32.8.0.5.48.1.18.130:-->16805888
fcsPortPhyPortNum.1.32.9.0.5.48.1.18.130:-->16809984
fcsPortPhyPortNum.1.32.10.0.5.48.1.18.130:-->16814080
fcsPortPhyPortNum.1.32.11.0.5.48.1.18.130:-->16818176
fcsPortPhyPortNum.1.32.12.0.5.48.1.18.130:-->16822272
fcsPortPhyPortNum.1.32.14.0.5.48.1.18.130:-->16830464
fcsPortPhyPortNum.1.32.15.0.5.48.1.18.130:-->16834560
fcsPortPhyPortNum.1.32.16.0.5.48.1.18.130:-->16838656
fcsPortPhyPortNum.1.32.17.0.5.48.1.18.130:-->16842752
fcsPortPhyPortNum.1.32.18.0.5.48.1.18.130:-->16846848
fcsPortPhyPortNum.1.32.19.0.5.48.1.18.130:-->16850944
fcsPortPhyPortNum.1.32.20.0.5.48.1.18.130:-->16855040
fcsPortPhyPortNum.1.32.21.0.5.48.1.18.130:-->16859136
fcsPortPhyPortNum.1.32.22.0.5.48.1.18.130:-->16863232
fcsPortPhyPortNum.1.32.23.0.5.48.1.18.130:-->16867328
fcsPortPhyPortNum.1.32.24.0.5.48.1.18.130:-->16871424
fcsPortPhyPortNum.1.32.25.0.5.48.1.18.130:-->16875520 <-- attach index 3 fcsPortPhyPortNum.1.32.26.0.5.48.1.18.130:-->16879616
fcsPortPhyPortNum.1.32.27.0.5.48.1.18.130:-->16883712
fcsPortPhyPortNum.1.32.28.0.5.48.1.18.130:-->16887808
fcsPortPhyPortNum.1.32.29.0.5.48.1.18.130:-->16891904
fcsPortPhyPortNum.1.32.30.0.5.48.1.18.130:-->16896000
fcsPortPhyPortNum.1.32.31.0.5.48.1.18.130:-->16900096
fcsPortPhyPortNum.1.32.32.0.5.48.1.18.130:-->16904192
fcsPortPhyPortNum.1.32.33.0.5.48.1.18.130:-->16908288
fcsPortPhyPortNum.1.32.34.0.5.48.1.18.130:-->16912384
fcsPortPhyPortNum.1.32.35.0.5.48.1.18.130:-->16916480
fcsPortPhyPortNum.1.32.36.0.5.48.1.18.130:-->16920576
fcsPortPhyPortNum.1.32.37.0.5.48.1.18.130:-->16924672
fcsPortPhyPortNum.1.32.38.0.5.48.1.18.130:-->16928768
fcsPortPhyPortNum.1.32.39.0.5.48.1.18.130:-->16932864
fcsPortPhyPortNum.1.32.40.0.5.48.1.18.130:-->16936960
fcsPortPhyPortNum.4094.32.13.0.5.48.1.18.130:-->16826368

Decode the ifIndex to get the slot / port information.

**********************************************************************************