SNMP::...lLucent(3pm)

💖 SNMP::Info::Layer3::AlcatelLucent(3pm) 💖

okay bestie, gather round, because we're about to get intimately acquainted with the SNMP::Info::Layer3::AlcatelLucent page from the SNMP::...lLucent(3pm) manual — yes the header truncates it like that, it's giving mysterious. anyway. it's a Perl module page, it's a subclass, and it's genuinely iconic.

🌸 NAME 🌸

SNMP::Info::Layer3::AlcatelLucent — your SNMP Interface to Alcatel-Lucent OmniSwitch. that's the whole vibe. 💅

🫶 AUTHOR 🫶

Bill Fenner. say thank you to Bill. 👑

---

✨ SYNOPSIS ✨

here's the little starter pack, copy it exactly, don't freestyle:

# Let SNMP::Info determine the correct subclass for you.
my $alu = new SNMP::Info(
                       AutoSpecify => 1,
                       Debug       => 1,
                       # These arguments are passed directly to SNMP::Session
                       DestHost    => 'myswitch',
                       Community   => 'public',
                       Version     => 2
                       )
   or die "Can't connect to DestHost.\n";

my $class      = $alu->class();
print "SNMP::Info determined this device to fall under subclass : $class\n";

so AutoSpecify => 1 means you don't have to do the homework, SNMP::Info sniffs out the subclass itself. Debug => 1 is your yapping mode. and DestHost, Community, Version go straight through to SNMP::Session, no middleman. if it can't connect? die "Can't connect to DestHost.\n". periodt.

🦋 DESCRIPTION 🦋

this is the subclass for Alcatel-Lucent OmniSwitch devices. that's the energy. 🎀

🧚 Inherited Classes 🧚

• SNMP::Info::Layer3
• SNMP::Info::MAU
• SNMP::Info::LLDP

she's got ancestors and they're all serving.

🌈 Required MIBs 🌈

• ALCATEL-IND1-DEVICES
• ALCATEL-IND1-CHASSIS-MIB
• ALU-POWER-ETHERNET-MIB

⚠️ okay listen, this one's important: Alcatel-Lucent distributes their own proprietary version of the POWER-ETHERNET-MIB, but the MIB module name they ship it under is just plain POWER-ETHERNET-MIB. so you have to hand-edit it, bestie, hand-edit it, and change the module name to ALU-POWER-ETHERNET-MIB so it can coexist peacefully with the standard POWER-ETHERNET-MIB. two MIBs, same name, one file, chaos. 💀

💜 Inherited Classes' MIBs 💜

• See "Required MIBs" in SNMP::Info::Layer3 for its own MIB requirements.
• See "Required MIBs" in SNMP::Info::MAU for its own MIB requirements.
• See "Required MIBs" in SNMP::Info::LLDP for its own MIB requirements.

---

👑 GLOBALS 👑

these are the methods that return a scalar value from SNMP. one value, one moment, main character energy.

• $alu->vendor() — returns 'alcatel-lucent'. that's it, that's the answer. 💅
• $alu->model() — tries to reference $alu->id() to one of the product MIBs listed up above. then it removes 'device' from the name for readability, because we're not doing that. ✨
• $alu->os() — returns 'AOS'.
• $alu->os_ver() — grabs the OS version from "sysDescr".
• $alu->ps1_type() — returns the type of the first power supply, from the ENTITY-MIB.
• $alu->ps2_type() — returns the type of the second power supply, from the ENTITY-MIB.
• $alu->ps1_status() — returns the status of the first power supply, from the ALCATEL-IND1-CHASSIS-MIB.
• $alu->ps2_status() — returns the status of the second power supply, from the ALCATEL-IND1-CHASSIS-MIB.

💖 Global Methods imported from SNMP::Info::Layer3 💖

See documentation in "GLOBALS" in SNMP::Info::Layer3 for details.

💖 Global Methods imported from SNMP::Info::MAU 💖

See documentation in "GLOBALS" in SNMP::Info::MAU for details.

💖 Global Methods imported from SNMP::Info::Layer3 💖

See documentation in "GLOBALS" in SNMP::Info::Layer3 for details.

😭 no bestie you're not seeing double, SNMP::Info::Layer3 really is listed twice up there in the globals imports. we keep it. we don't question it. it's iconic behaviour.

---

⭐ TABLE METHODS ⭐

these ones return tables of info — as a reference to a hash, obviously. little data structures, big feelings.

• $alu->interfaces() — returns the interface name from "ifName", because the default return value of "ifDescr" includes the OS version and we simply cannot. 🙈
• $alu->bp_index() — works around various bugs in the BRIDGE-MIB and Q-BRIDGE-MIB implementations, by returning both "ifIndex" and "dot1dBasePort" mappings to "ifIndex" values. yes both. we're built different.
• $alu->i_duplex_admin() — returns info from MAU-MIB.
• $alu->i_speed_admin() — returns info from MAU-MIB.
• $alu->peth_port_ifindex() — returns the "ifIndex" value for power-ethernet ports using the OmniSwitch algorithm. it's giving proprietary.

💙 Table Methods imported from SNMP::Info::Layer3 💙

See documentation in "TABLE METHODS" in SNMP::Info::Layer3 for details.

💙 Table Methods imported from SNMP::Info::MAU 💙

See documentation in "TABLE METHODS" in SNMP::Info::MAU for details.

💙 Table Methods imported from SNMP::Info::LLDP 💙

See documentation in "TABLE METHODS" in SNMP::Info::LLDP for details.

---

and that's the page, bestie 🫶 this was perl v5.40.1, dated 2026-02-28, living under the SNMP::...lLucent(3pm) manual — go forth and poll responsibly. 💖✨🎀