SCTE-HMS-HMTS-MIB Table View

This table contains entries to control multicast groups for
alarm collection.  This table allows for multiple groups of
alarms to be collected.  It is expected that a higher level
manager will add entries to this table and the transponders
multicast address table.  When trap contention modes are used
polling will be disable while an active entry in this table has
contention enabled.  This way the polling does not interfere with
the possible asynchronous notifications.  As default this table
shall have one entry, containing the broadcast address.  This is
a non-volatile table.

The forward port table contains information about the forward
transmitter ports of the HMTS.  The ports may be of several
varieties.  The majority of the control fields apply to the RF
serial port types, which support the HMS physical and MAC
layers.

The Reverse Port table contains information about the receiver
ports of the HMTS.  The reverse path may be Serial RF,
RS-485 or another serial interface.  The serial RF port is
usually a reverse path RF modem.  A unique identifier,
hmtsRevPortId, indexes this table.

The Device Table is the repository of all information known
about each transponder.  The termination system keeps track of
this information base on MAC Address.  The device table is an
unabridged list of information.
          
The contents of the entries in this table are non-volatile.

This table identifies the MAC addresses of devices that have a
problem in registering or communicating with the HMTS.  Only
devices with hmtsDevComStat value other than noError(1) will
have entries in this table.
          
It is the responsability of the HMTS to keep the contents of the
hmtsDevTable, hmtsComFaultTable, hmtsIPDevTable and hmtsCommDevTable
consistent according to the following rules:
- For each active row in hmtsDevTable whose hmtsDevComStat instance
  is different of noError(1), there must be a row with the same
  physical address in hmtsComFaultTable.
- For each row in hmtsComFaultTable, there must be a
  corresponding row in hmtsDevTable with RowStatus active.
- Each active row in the hmtsDevTable that has a valid IP address 
  must also be present in the hmtsIPDevTable.
- For each row in hmtsIPDevTable there must be a corresponding
  row in hmtsDevTable with rowstatus active.
- Each active row in the hmtsDevTable that has a valid community
  string and whose RowStatus is active must also be present in
  hmtsCommDevTable.
- For each row that exists in hmtsCommDevTable there must
  exist a row with the same community string in hmtsDevTable with
  RowStatus active.
- An IP address is valid if there does not exist another row in the
  hmtsDevTable with the same IP address and RowStatus active, and if
  it has been assigned by either an external DHCP server, the
  internal DHCP server (if hmtsIPManagementMethod is set to client)
  or if it fits in one of the ranges defined by hmtsNetAddrTable
  (if hmtsIPManagementMethod is set to manualXP, manualHMTS or
  automatic).
- A community string is valid if there does not exist another row in
  the hmtsDevTable with the same community string and RowStatus
  active.

The multicast address table lists the known multicast/broadcast
MAC addresses and provides a translation to either an IP address
or a community string.
The entries in this table are non-volatile.

The IP address is the index to this view of the hmtsDevTable.
Only the devices that have a device state of registered are
listed in this view.  This table is current for HMTS that
support the IP proxy as defined in SCTE 25-2 (Formerly HMS004).
          
It is the responsability of the HMTS to keep the contents of the
hmtsDevTable, hmtsComFaultTable, hmtsIPDevTable and hmtsCommDevTable
consistent according to the following rules:
- For each active row in hmtsDevTable whose hmtsDevComStat instance
  is different of noError(1), there must be a row with the same
  physical address in hmtsComFaultTable.
- For each row in hmtsComFaultTable, there must be a
  corresponding row in hmtsDevTable with RowStatus active.
- Each active row in the hmtsDevTable that has a valid IP address 
  must also be present in the hmtsIPDevTable.
- For each row in hmtsIPDevTable there must be a corresponding
  row in hmtsDevTable with rowstatus active.
- Each active row in the hmtsDevTable that has a valid community
  string and whose RowStatus is active must also be present in
  hmtsCommDevTable.
- For each row that exists in hmtsCommDevTable there must
  exist a row with the same community string in hmtsDevTable with
  RowStatus active.
- An IP address is valid if there does not exist another row in the
  hmtsDevTable with the same IP address and RowStatus active, and if
  it has been assigned by either an external DHCP server, the
  internal DHCP server (if hmtsIPManagementMethod is set to client)
  or if it fits in one of the ranges defined by hmtsNetAddrTable
  (if hmtsIPManagementMethod is set to manualXP, manualHMTS or
  automatic).
- A community string is valid if there does not exist another row in
  the hmtsDevTable with the same community string and RowStatus
  active.

This table provides a list of networks from which the HMTS
may select an IP address to automatically assign to a device.
This table shall also be used to verify manually entered
IP addresses (Device or Multicast) and IP Address originating
from the transponders. This table will be ignored by the HMTS
when hmtsIPManagementMethod is set to client.
          
This table is mandatory if the HMTS
supports IP address assignment as described in
hmtsIPManagementMethod.
          
Changing an existing entry in this table may cause IP address
currently in use to become invalid.  The HMTS shall support the
reassignment of IP addresses, by reassigning IP addresses of
devices that no longer have valid IPs.  How this is accomplished
is vender specific.
          
This is a non-volatile table.

The Community String is the index to this view of the
hmtsDevTable.  Only the devices that have successfully
registered at least once are listed in this view.  This table is
current for HMTS that support the community string proxy as
defined in SCTE 25-2 (Formerly HMS004).
          
It is the responsability of the HMTS to keep the contents of the
hmtsDevTable, hmtsComFaultTable, hmtsIPDevTable and hmtsCommDevTable
consistent according to the following rules:
- For each active row in hmtsDevTable whose hmtsDevComStat instance
  is different of noError(1), there must be a row with the same
  physical address in hmtsComFaultTable.
- For each row in hmtsComFaultTable, there must be a
  corresponding row in hmtsDevTable with RowStatus active.
- Each active row in the hmtsDevTable that has a valid IP address 
  must also be present in the hmtsIPDevTable.
- For each row in hmtsIPDevTable there must be a corresponding
  row in hmtsDevTable with rowstatus active.
- Each active row in the hmtsDevTable that has a valid community
  string and whose RowStatus is active must also be present in
  hmtsCommDevTable.
- For each row that exists in hmtsCommDevTable there must
  exist a row with the same community string in hmtsDevTable with
  RowStatus active.
- An IP address is valid if there does not exist another row in the
  hmtsDevTable with the same IP address and RowStatus active, and if
  it has been assigned by either an external DHCP server, the
  internal DHCP server (if hmtsIPManagementMethod is set to client)
  or if it fits in one of the ranges defined by hmtsNetAddrTable
  (if hmtsIPManagementMethod is set to manualXP, manualHMTS or
  automatic).
- A community string is valid if there does not exist another row in
  the hmtsDevTable with the same community string and RowStatus
  active.