The following Upstream Triggered Spectrum Capture bulk data control objects and MIBs are supported for PNM:
-
PNM Bulk Data Control Objects OID: 1.3.6.1.4.1.4491.2.1.27.1.1.1
-
PNM BULK DATA CONTROL OID: 1.3.6.1.4.1.4491.2.1.27.1.1.1.X
Where X is the bulk data transfer control parameter.
-
The Bulk Data Transfer (BDT) control objects that are supported are the IPaddress type, BDT server IP and BDT destination
path. This indicates to the CCAP the location where the capture results files are sent through TFTP transfer. In CBR8, the
TFTP transfer is done through IOX container and as such, other BDT objects aren’t relevant to this design model. IP address
type can be automatically set by CCAP based on the server IP value specified.
-
The following are the enumerated values for BDT for PNM:
-
Set the BDT IPv4 IP address type and TFTP IP address.
-
snmpr commands:
-
server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 -o 20:01:0d:b8
docsPnmBulkDestIpAddr.0 = 20 01 0d b8
-
server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0
docsPnmBulkDestIpAddrType.0 = ipv4(1)
-
server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0
docsPnmBulkDestIpAddr.0 = 20 01 0d b8
-
net-snmp commands:
-
server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x 20010db8
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8
-
server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.1.0 = INTEGER: 1
-
server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8
-
Set the BDT IPv6 IP address type and TFTP IP address.
-
snmpr commands:
-
server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 -o 20:01:0d:b8:85:a3:00:00:00:00:8a:2e:03:70:73:11
docsPnmBulkDestIpAddr.0 = 2001 0db8 85a3 0000 0000 8a2e 0370 7311
-
server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0
docsPnmBulkDestIpAddrType.0 = ipv6(2)
-
server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0
docsPnmBulkDestIpAddr.0 = 2001 0db8 85a3 0000 0000 8a2e 0370 7311
-
net-snmp commands:
-
server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x 20010db885a3000000008a2e03707311
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8 85 A3 00 00 00 00 8A 2E 03 70 73 11
server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.1.0 = INTEGER: 2
-
server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8 85 A3 00 00 00 00 8A 2E 03 70 73 11
-
Set the BDT destination TFTP path.
-
snmpr commands:
-
server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 -o pnm
docsPnmBulkDestPath.0 = pnm
-
server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0
docsPnmBulkDestPath.0 = pnm
-
net-snmp commands:
-
server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 s ‘pnm/test’
SSNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.3.0 = STRING: "pnm/test"
-
server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.3.0 = STRING: "pnm/test"
Multiple TFTP Servers Support for PNM BDT SNMP Infra
In releases before Cisco IOS XE Cupertino 17.9.1y, only one BDT TFTP destination server per CCAP is supported to store the
captured UTSC or RxMER data, and maximum eight captures on upstream ports per line card and a maximum of 20 captures per CBR8
is supported for both I-CMTS and RPHY. All captured files are stored into the same TFTP server.
-
Starting with Cisco IOS XE Cupertino 17.9.1y, the new PNM BDT MIB (docsPnmBulkDataTransferCfgTable) support has been added.
It introduces support for multiple TFTP destination servers, and simultaneous capture of both UTSC freerun and RxMER data
and store into different TFTP server locations. PNM captured files can be stored in three different TFTP servers simultaneously.
Each TFTP server detail is stored into BDT table using unique index values (that is, 1, 2 and 3).
-
The existing PNM Bulk Data Control Table MIB remains supported with the following changes.
-
Capture doesn’t start if the destination TFTP IP address and PATH aren’t configured.
-
For UTSC other mode, the path isn’t required and only IP is required.
-
Starting with Cisco IOS XE Cupertino 17.9.1y, PNM BulkData Transfer Cfg MIB and the legacy PNM Bulk Data Control MIB, can
be configured and used at the same time.
The captured UTSC or RxMER data are stored into the same TFTP server or different TFTP servers. This is done based on the
destination index mappings between BDT table and RxMER or UTSC configuration settings. The destination index is configured
as part of the docsPnmCmtsUtscCfgTable for UTSC and docsPnmCmtsUsOfdmaRxMerTable for Rxmer captures and should map to one
of the indices created in the BDT table - docsPnmBulkDataTransferCfgTable. So based on this destination index mapping, captured
data is stored into respective TFTP server locations.
LCs can run captures as long the max limit per LC and per cBR-8 aren’t exceeded but only using one of the three allowed TFTP
servers. That is, there’s no restriction that a server can be mapped to only one utsc capture config at a time, the same server
can be mapped to different type of captures
A BDT table entry may be modified at any given time. However, if there’s a capture running using the BDT entry, the capture
continues to run with the prior TFTP information with which it was started. The updated BDT details take effect only for new
captures which started after that update.
Proactive Network Management
Basic Infrastructure to Support Multiple TFTP Servers
PNM CCAP Bulk File Transfer Objects
The following are the DataTransferCfg MIB objects specified in DOCS-PNM-MIB in CM-SP-CCAP-OSSIv3.1-I23-220216 spec and these
MIB objects is used to support multiple TFTP destination servers to upload the captured UTSC and RxMER data from cBR-8.
Table 3. PNM CCAP Bulk File Transfer Objects
CCAP bulk data control Objects
|
OID
|
Supported |
docsPnmBulkFileTransfer |
1.3.6.1.4.1.4491.2.1.27.1.1.3 |
Yes |
docsPnmBulkDataTransferCfgTable |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1 |
Yes |
docsPnmBulkDataTransferCfgEntry |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1 |
Yes |
docsPnmBulkDataTransferCfgDestIndex |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.1 |
Yes |
docsPnmBulkDataTransferCfgDestHostname |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2 |
No |
docsPnmBulkDataTransferCfgDestHostIpAddrType |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3 |
Yes |
docsPnmBulkDataTransferCfgDestHostIpAddress |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4 |
Yes |
docsPnmBulkDataTransferCfgDestPort |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5 |
No |
docsPnmBulkDataTransferCfgDestBaseUri |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6 |
Yes |
docsPnmBulkDataTransferCfgProtocol |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7 |
No |
docsPnmBulkDataTransferCfgLocalStore |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8 |
No |
docsPnmBulkDataTransferCfgRowStatus |
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9 |
Yes |
The destination port and protocol are set to default values which are shown below, it only has read access.
UTSC Config Table Object
The new objects below are added to the existing UTSC Capture config table as mentioned in the spec but the object which is
relevant to DataTransferCfg
is supported as shown in the following table.
Table 4. UTSC Config Table Object
UTSC docsPnmCmtsUtscCfgTable Objects
|
OID
|
Supported
|
docsPnmCmtsUtscCfgDestinationIndex |
1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.24 |
Yes |
Upstream OFDMA RxMER table object
The following new object is added to the existing Upstream OFDMA RxMER table:
Table 5. Upstream OFDMA RxMER table object
docsPnmCmtsUsOfdmaRxMerTable object
|
OID
|
Supported
|
docsPnmCmtsUsOfdmaRxMerDestinationIndex |
1.3.6.1.4.1.4491.2.1.27.1.3.7.1.7 |
Yes |
Legacy PNM Bulk Data Control Objects
The legacy docsPnmBulkCtl objects continue to be supported for all capture types with a Guest shell design.
Table 6. Legacy PNM Bulk Data Control Objects
docsPnmCmtsUsOfdmaRxMerTable object
|
OID
|
docsPnmBulkDestIpAddrType |
1.3.6.1.4.1.4491.2.1.27.1.1.1.1 |
docsPnmBulkDestIpAddr |
1.3.6.1.4.1.4491.2.1.27.1.1.1.2 |
docsPnmBulkDestPath |
1.3.6.1.4.1.4491.2.1.27.1.1.1.3 |
docsPnmBulkUploadControl
|
1.3.6.1.4.1.4491.2.1.27.1.1.1.4 |
The IP type and upload control are set to default values as shown below, it only has read access.
-
docsPnmBulkDestIpAddrType
is automatically set as the IPV4 (1)/IPV6(2), will be set automatically while configuring ipv4 or ipv6 address.
-
docsPnmBulkUploadControl
is set to default as autoupload (3).
Note
|
Thi object only read-access. You cannot modify the value via the snmpset command.
|
UTSC/RxMER capture is blocked to start capture if Destination IP address and PATH aren’t configured.
Note
|
The CM-MAC or OTHER mode capture types aren’t supported with docsPnmBulkDataTransferCfg MIB.
|
PNM UTSC/RxMER Config Destination Index
The BDT and UTSC/RxMER configs are linked using below destination the docsPnmCmtsUtscCfgDestinationIndex
and docsPnmCmtsUsOfdmaRxMerDestinationIndex
indices with the default index values as 0xFFFFFFFF.
You need to configure this index to one of the valid BDT config indexes. If capture is started with default index value,
then it uses TFTP server details configured using Legacy MIBs. If valid BDT index is mapped, then it uses the TFTP server
details configured in that BDT index. Capture can’t be started if the row status of the mapped BDT index isn’t in ACTIVE state.
PNM BDT MIB Details
docsPnmBulkDataTransferCfgTable DocsPnmBulkDataTransferCfgEntry.[DestIndex]
BDT MIB table rows are created with unique index value from 1 to 3 to store three different TFTP server details. In CBR8,
the following BDT objects are supported.
Table 7. PNM BDT MIB Details
OBJECTS
|
Supported
|
docsPnmBulkDataTransferCfgDestHostname |
NO |
docsPnmBulkDataTransferCfgDestHostIpAddrType |
YES |
docsPnmBulkDataTransferCfgDestHostIpAddress |
YES |
docsPnmBulkDataTransferCfgDestPort |
NO |
docsPnmBulkDataTransferCfgDestBaseUri |
YES |
docsPnmBulkDataTransferCfgProtocol |
NO |
docsPnmBulkDataTransferCfgLocalStore |
NO |
docsPnmBulkDataTransferCfgRowStatus |
YES |
-
docsPnmBulkDataTransferCfgDestHostIpAddrType
: To set IP types either IPV4 (1) and IPV6 (2)
-
docsPnmBulkDataTransferCfgDestHostIpAddress
: To set IPV4/IPV6 address in hex value. Configure BDT URI in this format - tftp://{tftp_ip}/{tftp_path}
.
-
docsPnmBulkDataTransferCfgDestBaseUri
: To set IPV4/IPV6 address and PATH details in TFTP URL format.
-
docsPnmBulkDataTransferCfgRowStatus
: To create or update or delete a row in BDT table.
-
docsPnmBulkDataTransferCfgProtocol
: This object is hardcoded, same for port and supported for read.
Rows can be created with createandgo and createandwait.
If created with “createandgo then one time mandatory configs (ip address and Uri) are configured, and then row is moved to ACTIVE
state automatically, else it remains in NOT READY
state.
If created with createandwait then one time mandatory configs (ip address and Uri) are configured, and then row is moved to NotInUse
state and user need to configure the row to ACTIVE
state manually.
SUPHA, LCHA, and LCPR
SUPHA - All BDT MIB configs get erased on SUPSO, you need to reconfigure the BDT rows with all required details.
LCHA/LCPR - BDT MIB runs in SUP IOSd process so BDT configs remain intact after LCHA/LCPR.
The following is an example of the steps required for PNM BDT configuration.
-
Row: Create a BDT entry.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 4
-
IP Type: Set an IP type.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 i 1
-
IP/IPV6 address: Set IPV4/IPV6 address.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 x C0A8648C
-
Uri: Set TFTP URL format.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 s tftp://192.168.100.140/pnm1
Note
|
You must configure both TFTP IP and BDT URI to initiate the UTSC capture.
|
RPHY#test cable pnm bdt config get-ip
BDT TABLE ip addresses:
The destination index : 1
The assigned IP is type : 1
IPv4: 192.168.100.140
IPv6: ---
BDT V0 TFTP details:
The assigned IP is type: 0
IPv4: ---
IPv6: ---
CHN3-RACK3-RPHY#test cable pnm bdt config get-path
BDT TABLE TFTP path:
Destination Index = 1 : TFTP path is = tftp://192.168.100.140/pnm1
BDT V0 TFTP Path:
oob-auto@oob-auto:/tftpboot/pnm1$ snmpwalk -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2.1 = ""
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 = Hex-STRING: C0 A8 64 8C
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5.1 = Gauge32: 69
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 = STRING: "tftp://192.168.100.140/pnm1"
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8.1 = INTEGER: 0
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 = INTEGER: 1
oob-auto@oob-auto:/tftpboot/pnm1$
To Delete a row:
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 6
PHY#test cable pnm bdt config get-ip
BDT TABLE ip addresses:
BDT V0 TFTP details:
The assigned IP is type: 0
IPv4: ---
IPv6: ---
RPHY#test cable pnm bdt config get-path
BDT TABLE TFTP path:
BDT V0 TFTP Path:
RPHY#
The following example shows PNM BDT dest index mapping to UTSC configs.
-
UTSC destination index should be set to BDT index before starting the capture. If destination index is not set in UTSC (DocsPnmCmtsUtscCfgEntry),
it uses the legacy PNM Bulk Data objects for getting the TFTP details.
-
RxMER destination index should be set to BDT index before starting the capture. If not set it uses the legacy TFTP infra.
If destination index is not set in RxMER table (DocsPnmCmtsUsOfdmaRxMerEntry) , it uses the legacy PNM Bulk Data objects for
TFTP purpose.
Before setting BDT index:
RPHY#test cable pnm uts configure show 0 client-id 1 2/0/0
Acquire capcfg for capture entry success, ret: No error
Capture Config params for client 1 on clc 2/0/0
utsc config index 1
BDT TFTP dest index FFFFFFFF
physical channel 0
logical channel 0
snmp ifIndex 490350
trigger-mode freerun
frequency 70000000
span 30000000
bins 4096
window mode blackman-harris
output format fft-pwr
repeat-period 50000
duration 500000
trigger-count 0
capcfg entry status active
minislot count 0
sid 0
timestamp 0
cm-mac 0000.0000.0000
averaging 0
qualify frequency 0
qualify bandwidth 5120000
qualify threshold -100
RPHY#
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.24.490446.1 u 1
RPHY#test cable pnm uts configure show 0 client-id 1 2/0/0
Acquire capcfg for capture entry success, ret: No error
Capture Config params for client 1 on clc 2/0/0
utsc config index 1
BDT TFTP dest index 1
physical channel 0
logical channel 0
snmp ifIndex 490350
trigger-mode freerun
frequency 70000000
span 30000000
bins 4096
window mode blackman-harris
output format fft-pwr
repeat-period 50000
duration 500000
trigger-count 0
capcfg entry status active
minislot count 0
sid 0
timestamp 0
cm-mac 0000.0000.0000
averaging 0
qualify frequency 0
qualify bandwidth 5120000
qualify threshold -100
RPHY#
Before setting BDT index:
RPHY#test cable pnm rxmer show-job-list
Job Client ifIndex CM-Mac Status Enable Pre-Eq Num-Avgs Retry BdtDestIndex
--------------------------------------------------------------------------------------------------
0 SNMP 490350 9058.515c.a3e8 INACTIVE N N 1 0 FFFFFFFF
PNM RxMER job count 1
RPHY#
After setting BDT index:
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.3.7.1.7.490350 u 1
RPHY#test cable pnm rxmer show-job-list
Job Client ifIndex CM-Mac Status Enable Pre-Eq Num-Avgs Retry BdtDestIndex
--------------------------------------------------------------------------------------------------
0 SNMP 490350 9058.515c.a3e8 INACTIVE N N 1 0 1
PNM RxMER job count 1
RPHY#
Successful creation for three rows:
oob-auto@oob-auto:/tftpboot/pnm1$
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 4
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 = INTEGER: 4
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 i 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 = INTEGER: 1
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 x C0A8648C
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 = Hex-STRING: C0 A8 64 8C
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 s tftp://192.168.100.140/pnm1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 = STRING: "tftp://192.168.100.140/pnm1"
oob-auto@oob-auto:/tftpboot/pnm1$
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.2 i 4
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.2 = INTEGER: 4
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.2 i 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.2 = INTEGER: 1
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.2 x C0A8648D
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.2 = Hex-STRING: C0 A8 64 8D
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.2 s tftp://192.168.100.141/pnm2
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.2 = STRING: "tftp://192.168.100.141/pnm2"
oob-auto@oob-auto:/tftpboot/pnm1$
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.3 i 4
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.3 = INTEGER: 4
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.3 i 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.3 = INTEGER: 1
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.3 x C0A8648E
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.3 = Hex-STRING: C0 A8 64 8E
oob-auto@oob-auto:/tftpboot/pnm1$
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.3 s tftp://192.168.100.142/pnm3
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.3 = STRING: "tftp://192.168.100.142/pnm3"
oob-auto@oob-auto:/tftpboot/pnm1$
Snmpwalk of three BDT rows
oob-auto@oob-auto:/tftpboot/pnm1$ snmpwalk -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2.1 = ""
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2.2 = ""
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2.3 = ""
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.2 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.3 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 = Hex-STRING: C0 A8 64 8C
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.2 = Hex-STRING: C0 A8 64 8D
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.3 = Hex-STRING: C0 A8 64 8E
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5.1 = Gauge32: 69
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5.2 = Gauge32: 69
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5.3 = Gauge32: 69
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 = STRING: "tftp://192.168.100.140/pnm1"
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.2 = STRING: "tftp://192.168.100.141/pnm2"
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.3 = STRING: "tftp://192.168.100.142/pnm3"
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7.2 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7.3 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8.1 = INTEGER: 0
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8.2 = INTEGER: 0
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8.3 = INTEGER: 0
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.2 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.3 = INTEGER: 1
Legacy PNM MIB configuration and snmpwalk:
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x C0A8648C
iso.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 = Hex-STRING: C0 A8 64 8C
oob-auto@oob-auto:/tftpboot/pnm1$ snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 s pnm1
iso.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 = STRING: "pnm1"
oob-auto@oob-auto:/tftpboot/pnm1$
oob-auto@oob-auto:/tftpboot/pnm1$ snmpwalk -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.1
iso.3.6.1.4.1.4491.2.1.27.1.1.1.1.0 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 = Hex-STRING: C0 A8 64 8C
iso.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 = STRING: "pnm1"
iso.3.6.1.4.1.4491.2.1.27.1.1.1.4.0 = INTEGER: 3
oob-auto@oob-auto:/tftpboot/pnm1$
oob-auto@oob-auto:/tftpboot/pnm1$