Reference record for OID 1.3.6.1.4.1.866.20.1.30.1


parent
1.3.6.1.4.1.866.20.1.30 (fcVirtualPorts)
node code
1
node name
fcvVirtualPortTable
dot oid
1.3.6.1.4.1.866.20.1.30.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) pce(866) frxSoftware(20) frxConfig(1) fcVirtualPorts(30) fcvVirtualPortTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) pce(866) frxSoftware(20) frxConfig(1) fcVirtualPorts(30) fcvVirtualPortTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) pce(866) frxSoftware(20) frxConfig(1) fcVirtualPorts(30) fcvVirtualPortTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) pce(866) frxSoftware(20) frxConfig(1) fcVirtualPorts(30) fcvVirtualPortTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) pce(866) frxSoftware(20) frxConfig(1) fcVirtualPorts(30) fcvVirtualPortTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) pce(866) frxSoftware(20) frxConfig(1) fcVirtualPorts(30) fcvVirtualPortTable(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/pce/frxSoftware/frxConfig/fcVirtualPorts/fcvVirtualPortTable
  • /iso/identified-organization/dod/internet/private/enterprises/pce/frxSoftware/frxConfig/fcVirtualPorts/fcvVirtualPortTable
  • /iso/org/dod/internet/private/enterprise/pce/frxSoftware/frxConfig/fcVirtualPorts/fcvVirtualPortTable
  • /iso/org/dod/internet/private/enterprises/pce/frxSoftware/frxConfig/fcVirtualPorts/fcvVirtualPortTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/pce/frxSoftware/frxConfig/fcVirtualPorts/fcvVirtualPortTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/pce/frxSoftware/frxConfig/fcVirtualPorts/fcvVirtualPortTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/866/20/1/30/1

    Description by mibdepot

    This table defines the virtual ports.

    Through a virtual port the bridge and the IP, IPX
    and CLNP routers can communicate with bridges and
    routers taking place inside a particular virtual
    network. These communications may use a Local Area
    Network (LAN), namely the virtual network matches
    the LAN, or Wide Area Networks (WAN), namely the
    virtual network matches a group of remote bridges
    or routers.

    Each module of the equipment has its own virtual
    ports. The module 0 can enable bridge forwarding,
    IP (Internet Protocol) routing, IPX (Internetwork
    Packet eXchange : Novell protocol) routing and
    CLNP (ConnectionLess Network Protocol) routing.
    The modules 1 and 2 can only act as IP host. So
    each of these two modules needs one remote VP when
    its SNMP agent must exchange SNMP datas with an
    SNMP manager.

    Set any writable object(s) of this table to valid
    value(s) with a new index value to create an entry
    (the objects of the entry not present in this SET
    REQUEST will take their default values). Set
    fcvVpStatus to 'invalid' to delete an entry.

    Parsed from file v42ami1e.mib.txt
    Company: None
    Module: PCE-MIB

    Description by circitor

    This table defines the virtual ports.

    Through a virtual port the bridge and the IP, IPX
    and CLNP routers can communicate with bridges and
    routers taking place inside a particular virtual
    network. These communications may use a Local Area
    Network (LAN), namely the virtual network matches
    the LAN, or Wide Area Networks (WAN), namely the
    virtual network matches a group of remote bridges
    or routers.

    Each module of the equipment has its own virtual
    ports. The module 0 can enable bridge forwarding,
    IP (Internet Protocol) routing, IPX (Internetwork
    Packet eXchange : Novell protocol) routing and
    CLNP (ConnectionLess Network Protocol) routing.
    The modules 1 and 2 can only act as IP host. So
    each of these two modules needs one remote VP when
    its SNMP agent must exchange SNMP datas with an
    SNMP manager.

    Set any writable object(s) of this table to valid
    value(s) with a new index value to create an entry
    (the objects of the entry not present in this SET
    REQUEST will take their default values). Set
    fcvVpStatus to 'invalid' to delete an entry.

    Parsed from file PCE-MIB.mib
    Module: PCE-MIB

    Information by oid_info

    Vendor: Philips Communication d'Entreprise Claude Lubin
    Module: PCE-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    fcvVirtualPortTable OBJECT-TYPE SYNTAX SEQUENCE OF FcvVirtualPortEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table defines the virtual ports. Through a virtual port the bridge and the IP, IPX and CLNP routers can communicate with bridges and routers taking place inside a particular virtual network. These communications may use a Local Area Network (LAN), namely the virtual network matches the LAN, or Wide Area Networks (WAN), namely the virtual network matches a group of remote bridges or routers. Each module of the equipment has its own virtual ports. The module 0 can enable bridge forwarding, IP (Internet Protocol) routing, IPX (Internetwork Packet eXchange : Novell protocol) routing and CLNP (ConnectionLess Network Protocol) routing. The modules 1 and 2 can only act as IP host. So each of these two modules needs one remote VP when its SNMP agent must exchange SNMP datas with an SNMP manager. Set any writable object(s) of this table to valid value(s) with a new index value to create an entry (the objects of the entry not present in this SET REQUEST will take their default values). Set fcvVpStatus to 'invalid' to delete an entry." ::= { fcVirtualPorts 1 }

    Information by circitor

    fcvVirtualPortTable OBJECT-TYPE SYNTAX SEQUENCE OF FcvVirtualPortEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table defines the virtual ports. Through a virtual port the bridge and the IP, IPX and CLNP routers can communicate with bridges and routers taking place inside a particular virtual network. These communications may use a Local Area Network (LAN), namely the virtual network matches the LAN, or Wide Area Networks (WAN), namely the virtual network matches a group of remote bridges or routers. Each module of the equipment has its own virtual ports. The module 0 can enable bridge forwarding, IP (Internet Protocol) routing, IPX (Internetwork Packet eXchange : Novell protocol) routing and CLNP (ConnectionLess Network Protocol) routing. The modules 1 and 2 can only act as IP host. So each of these two modules needs one remote VP when its SNMP agent must exchange SNMP datas with an SNMP manager. Set any writable object(s) of this table to valid value(s) with a new index value to create an entry (the objects of the entry not present in this SET REQUEST will take their default values). Set fcvVpStatus to 'invalid' to delete an entry." ::= { fcVirtualPorts 1 }

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.866.20.1.30.1.1 fcvVirtualPortEntry 4 4 An entry of fcvVirtualPortTable.

    Brothers (2)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.866.20.1.30.10 fcvLocalVirtualPorts 2 25 None
    1.3.6.1.4.1.866.20.1.30.20 fcvRemoteVirtualPorts 19 53 None