sfpsMcastCnxDestination |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.1 |
The multicast destination MAC address.
|
sfpsMcastCnxSource |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.2 |
The source MAC address.
|
sfpsMcastCnxSenderSw |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.3 |
The MAC address of the switch that the sender is on.
|
sfpsMcastCnxInPort |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.4 |
Local upstream port for flow.
|
sfpsMcastCnxOutPorts |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.5 |
Local downstream port(s) for flow.
|
sfpsMcastCnxGroup |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.6 |
Net layer ID of multicast group
|
sfpsMcastCnxTTL |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.7 |
Scope vlaue for this flow
|
sfpsMcastCnxAge |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.8 |
Age of local connection
|
sfpsMcastCnxStatus |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.9 |
Local connection status (bitwise)
|
sfpsMcastCnxNextSw |
.1.3.6.1.4.1.52.4.2.4.2.5.1.1.10 |
The MAC address of the next switch.
|
sfpsMcastCnxAPIDestination |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.1 |
Multicast destination MAC
|
sfpsMcastCnxAPISource |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.2 |
Multicast sender MAC
|
sfpsMcastCnxAPISenderSw |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.3 |
Mac of switch where sender is
|
sfpsMcastCnxAPIInPort |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.4 |
Local upstream port for flow
|
sfpsMcastCnxAPIOutPort |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.5 |
Local downstream port(s) for flow
|
sfpsMcastCnxAPIGroup |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.6 |
Net layer ID of multicast group
|
sfpsMcastCnxAPITTL |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.7 |
Scope value for this flow
|
sfpsMcastCnxAPIVerb |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.8 |
Action to take
|
sfpsMcastCnxAPIFilters |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.9 |
Count of local multicast filters
|
sfpsMcastCnxAPINonFilters |
.1.3.6.1.4.1.52.4.2.4.2.5.1.2.10 |
Count of local multicast connections
|
sfpsMcastIPRouterEntry |
.1.3.6.1.4.1.52.4.2.4.2.5.2.1.1.1 |
sfpsMcastIPRouterAPIVerb |
.1.3.6.1.4.1.52.4.2.4.2.5.2.1.2 |
Action to take
|
sfpsMcastIPRouterAPIIFNum |
.1.3.6.1.4.1.52.4.2.4.2.5.2.1.3 |
Port where multicast router is attached
|
sfpsMcastIPRouterAPIRouterIP |
.1.3.6.1.4.1.52.4.2.4.2.5.2.1.4 |
IP address of attached multicast router
|
sfpsMcastIPRouterAPITTLScope |
.1.3.6.1.4.1.52.4.2.4.2.5.2.1.5 |
Scope value for this router
|
sfpsMcastIPRouterAPIVlanId |
.1.3.6.1.4.1.52.4.2.4.2.5.2.1.6 |
sfpsMcastIPRIBEntry |
.1.3.6.1.4.1.52.4.2.4.2.5.2.3.1.1 |
sfpsMcastIPRIBApiGroup |
.1.3.6.1.4.1.52.4.2.4.2.5.2.3.2.1 |
CF IP address IP multicast group address
|
sfpsMcastIPRIBApiPort |
.1.3.6.1.4.1.52.4.2.4.2.5.2.3.2.2 |
Port number, -1 means all ports
|
sfpsMcastIPRIBApiVerb |
.1.3.6.1.4.1.52.4.2.4.2.5.2.3.2.3 |
Action to take
|
sfpsMcastConfigApiSenderTableSize |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.1 |
This is the number of entries that are allocated in the
multicast connection table at startup. Changing the
value will not take effect until blade is reset.
Values can be set between 0 and 2048.
|
sfpsMcastConfigApiMaxNonFilters |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.2 |
This number is currently not used. Its future purpose
may be to control the number of multi-outport connections
in use. Values can be set between 0 and 2048.
|
sfpsMcastConfigApiRDRetryBuffs |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.3 |
This number determines the number of packet objects that
will be allocated by the reliable control packet transport
agent. The packet object does not allocate space for the
packet, it just manages the packet delivery machine.
Each increment of this oid allocates space for 128
packet management objects which are 82 bytes in size.
Therefore each increment allocates about 10k of memory.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiRDPktBuffs |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.4 |
This number determines the number of packet buffers that
will be allocated by the reliable control packet transport
agent. Each increment of this oid allocates space for 128
packets which are 512 bytes in size.
Therefore each increment allocates about 65k of memory.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiPendingMaps |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.5 |
This is the number of delayed connection mappings that
will be maintained while waiting for topology changes
to be propagated or while waiting for interswitch
resolve. The effect of this setting is most evident
when a link or switch is lost thru which may multicast
connections were passing. An attempt to reconnect is made
after the delay specified in MC_CONFIG_API_REMAP_DELAY.
Only the number of MC_CONFIG_API_PENDING_MAPS will be
deferred. If you lose 100 connections and this number is
set to 20, at best you'll reconnect 20 streams after the
delay. The rest of the connections will be reestablished
after the receivers respond to sender announcements which
happen every MC_CONFIG_API_REFRESH_INTERVAL interval.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiSndrAgeOut |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.6 |
This is the interval in seconds that the age timer
runs. It is used to determine if a sender is still
sending. After one age out interval, the sender is
placed in a dying state and the local switch starts to
listen for traffic from that sender on a specific
destination. If any traffic is received, the sender
if placed back in a non-dying state. If no traffic
is seen before the second age interval, the sender is
considered dead and the corresponding connection tree
for that da/sa connection is removed throughout the
domain. Value will not take effect until blade is reset.
|
sfpsMcastConfigApiRefreshInterval |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.7 |
This is the interval at which sender announcements will be
transmitted by the switch that the sender is locally
attached. All sender refreshes will occur within 12 seconds.
If this number is set to 60, 1/2 of the senders will
be announced every 60 seconds. If this number is 30,
1/4 of the senders will be announced every 30 seconds.
If the number of senders grows, the refresh interval
may have to be adjusted shorter. The fine tuning is
to determine which is better, fewer-bigger announcements,
or more-smaller announcements.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiSndersPerAncmt |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.8 |
This is the number of sender announcements that will be
made before the thread is released.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiDebugLog |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.9 |
This value enables or disables extensive information
logging in IGMP and MCAST generics. It is used in
conjunction with the EventLogClient log flags. This
value should be 0 unless extensive diagnostic information
is required. This value is not persistent.
This setting takes effect immediately.
|
sfpsMcastConfigApiStaticTblSize |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.10 |
This is the number of static entries that can be made to
the sender database (multicast connection table).
Typically there would be no entries in this table.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiMcribSize |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.11 |
This is the number of static entries that can be made to
the receiver database. Typically there would be
very few entries in this table.
Value will not take effect until blade is reset.
|
sfpsMcastConfigApiMcastMode |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.12 |
Multicast operates in three vlan checking modes.
Mode 1 - Do no vlan checking. The sender and
receivers do not have to be on the same vlan.
Multicast connections in this mode disregard
whether or not the sender or receiver is in a
secure or open vlan.
Mode 2 - Do some vlan checking. This mode allows
connections to be established between any
sender/receivers on any vlan except for groups
using the 224.0.0.x range of ip multicast
addresses. These addresses are used for the
most part by routers which should only be
communicating to each other when they are
in the same vlan. Mode 2 restricts routers
to have the same port based vlan membership.
Mode 3 - Check all. The sender and receivers have
to be members of the same port based vlan.
This setting takes effect immediately. No existing
connections will be torn down.
|
sfpsMcastConfigApiRemapDelay |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.13 |
When attempting to obtain a path from receiver to sender,
a wait is sometimes incurred when pending on a switch
resolve response. Additionally, when topology events
occur that cause a redirection of the connection tree,
time must be allowed for the topology agents in the
domain to be notified before a new path can be
requested. This is the number of seconds that will
elaspe before remapping will be attempted.
This setting takes effect immediately.
|
sfpsMcastConfigApiQHighLimit |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.14 |
The default for the High Query Rate is 100
|
sfpsMcastConfigApiQLowLimit |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.15 |
The default for the low query rate is 20
|
sfpsMcastConfigApiDynamicQuery |
.1.3.6.1.4.1.52.4.2.4.2.5.4.1.16 |
The default for the dynamic query is 1 (enabled)
|
sfpsMcastIPSIBEntry |
.1.3.6.1.4.1.52.4.2.4.2.5.2.4.1.1 |
sfpsMcastIPSibApiGroup |
.1.3.6.1.4.1.52.4.2.4.2.5.2.4.2.1 |
sfpsMcastIPSibApiSender |
.1.3.6.1.4.1.52.4.2.4.2.5.2.4.2.2 |
sfpsMcastIPSibApiVerb |
.1.3.6.1.4.1.52.4.2.4.2.5.2.4.2.3 |