Unable to discover the Huawei stack switches

[Pritesh-TechM]

Hi All,

I am unable to discover the Huawei stack switches.

Its discovering single device instead of two(master and slave).

Master-Slave configration is done at device end but not getting in servicenow.

please help out me.

[AJ-TechTrek]

Hi @Pritesh-TechM ,

As per my understanding problem Summary is

* Huawei stacked switches (with master-slave configuration) are not fully discovered.
* Only one CI (typically the master) appears in the CMDB.
* You expect both stack members (master and slave) to be visible in ServiceNow.

Root Cause
By default:
* SNMP-based Discovery often picks up only the master node of a switch stack.
* Most standard SNMP probes focus on entity-level data, which doesn't distinguish between multiple stack members.
* Huawei stack MIBs (Management Information Bases) are not natively handled by ServiceNow Discovery patterns unless extended.

Recommended Solution Approach which might help you.

1. Confirm SNMP Access and Community String
* Run SNMP Walk using MID Server tool or CLI:
snmpwalk -v2c -c <community> <IP> .1
* Ensure the SNMP walk returns data for stack MIBs, such as:
* .1.3.6.1.4.1.2011.* — Huawei enterprise-specific MIBs
Look for stack member info under:
* hwStackMemberTable
* hwEntityPhysicalTable
* Or hwStackInfo

2. Extend SNMP Classifiers and Probes
A. Create a Custom SNMP Probe
* Create a custom SNMP probe targeting Huawei stack-specific OIDs.
* For example:
* Probe name: Custom - Huawei Stack Member Discovery
* Use OIDs like:
.1.3.6.1.4.1.2011.5.25.41.1.1.1.1.2 — stack member role
* .1.3.6.1.4.1.2011.5.25.41.1.1.1.1.3 — stack member ID
* .1.3.6.1.4.1.2011.5.25.41.1.1.1.1.4 — stack member description

B. Extend SNMP Patterns
* Use the Pattern Designer to:
* Parse SNMP responses
* Create child CIs or multiple CIs (based on stack members)
* Populate them under appropriate classes (e.g., cmdb_ci_network_adapter or cmdb_ci_switch)

3. Update Identification Rules (Optional)
If your probe/pattern can now discover both master and slave:
* Ensure your Identification Rules don’t merge them mistakenly as one CI.
* Consider using:
* Stack Member ID
* Chassis Serial
* Or Module Slot Number as part of the identifier

4. Relate Stack Members
* If multiple devices are discovered:
* Use a parent-child relationship
* Or add stack membership using Depends on::Used by relationship

Example Custom SNMP Probe Result Parse Logic
[
{
"member_id": "1",
"role": "Master",
"serial": "1234ABCD",
"model": "Huawei S5720-28X",
"ip": "10.1.1.10"
},
{
"member_id": "2",
"role": "Slave",
"serial": "5678EFGH",
"model": "Huawei S5720-28X",
"ip": "10.1.1.10"
}
]

Alternative Option: Use a Discovery Pattern with SNMP Table Parsing
1. In Pattern Designer:
* Select SNMP - Network Switch as the base pattern
* Add SNMP Table operation for the Huawei stack OIDs
2. Extract the table data
3. Create a CI for each row using Loop and Create Operations

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025