Sub-id and brg-id names with lengths between 32 and 64 characters

Beginning with Release 20.2.R1, the length of sub-id and brg-id names increased from 32 characters to 64 characters. These are referred to as long sub-id and long brg-id. The length of the corresponding RADIUS attributes, Alc-SubscID-Str and Alc-BRG-ID, that are mapped to the long sub-id and long brg-id are also increased to 64 characters.

As a result of this length increase, all MIB tables containing sub-id and brg-id names are affected. In a majority of those tables, the sub-id and brg-id name length is directly increased from 32 characters to 64 characters. However, tables where the MIB OID key contains a sub-id or brg-id as one of the fields do not increase the size of the sub-id and brg-id fields because the maximum key size of 128 characters could be exceeded when the sub-id and brg-id names are combined to form the key. Because the maximum size of the key in the MIB tables is limited to 128 characters, the sub-id and brg-id length in such tables remains limited to 32 characters. This ensures that the MIB key does not exceed the maximum size of 128 characters. This also means that an operator-defined sub-id and brg-id name that is greater than 32 characters must be internally translated (within the SR OS) into a 32-character identification. Instead of truncating sub-id and brg-id names that are greater than 32 characters to a 32 characters value (which could lead to duplicate sub-ids or brg-ids), an internal and unique 32-character length sub-id and brg-id is automatically generated by the system. These internally generated sub-id and brg-id names are used in the following tables where the long sub-id and brg-id (>32characters) could lead to violations of the maximum key size (128 characters). The affected tables are:

• TIMETRA-SUBSCRIBER-MGMT-MIB:

  • tmnxSLAProfInstOverridesEntry

  • tmnxSubSpiOvrEntry

  • tmnxSLAProfInstSubHostV2Entry

  • tmnxSubSpiHostEntry

  • tmnxSPICatEntry

  • tmnxSubSpiCatEntry

  • tmnxSpiEgrQosSchedStatsEntry

  • tmnxSPIEgrQosSchedStatsEntry

• TIMETRA-NAT-MIB:

  • tmnxNatL2AwHostPlcyEntry

  • tmnxNatFwlHostEntry

  • tmnxNatFwd2Entry

The operator-defined long sub-id and long brg-id names are listed in these tables and replaced with the internally-generated version with a 32-character length version.

Table: Potential violation of the maximum key size shows examples of sub-id and brg-id names where a long sub-id and long brg-id may lead to a violation of the maximum key size. The internally-generated ID begins with the _tmnx_ prefix:

The operator-defined sub-ids and brg-ids with lengths up to 32 characters are not affected by this change.

In most cases, operators are not concerned with the internal sub-id and brg-id which are only used by the system to access data in one of the 11 MIB tables where the long sub-id or long brg-id would otherwise violate the maximum length of the key. Therefore, the internal ID is not shown in the output of any show command.

An exception occurs when a SNMP table walk is performed in one of the 11 tables in which an entry of interest is found that contains an internal sub-id and brg-id, that needs to be connected with the real (long) subscriber identity.

This conversion can be performed and is aided by the MIB tables tmnxSubShortEntry (Table: tmnxSubShortEntry ) and tmnxSubBrgShortEntry tables (Table: tmnxSubBrgShortEntry ):

The mapping from long to an internal ID can be retrieved from the tmnxSubscriberInfoEntry (Table: tmnxSubscriberInfoEntry ) and tmnxSubBrgEntry (Table: tmnxSubBrgEntry ) tables: