Tell us your biggest pain point when troubleshooting IT issues, e.g. users complaining about slow or broken access to applications.
Select your biggest pain point from this list.
Of course any additional comment to this page would be great (e.g. second biggest, pain point not listed below...)
SolarWinds has Product Upgrade Advisor website which helps users to validate compatibility of product versions.https://customerportal.solarwinds.com/support/product-upgrade-advisor
Do you use that prior any product upgrade?
There was a feature request for a UDT recently for an automated port shutdown, if the connected endpoint is on the "black list".
What would be your other reasons, for which would you want to shut down the port? Lets's go our imagination wild and imagine events like user device infected by a non-deletable virus, peer-to-peer software installed, firewall disabled? Feel free to vote for Other and leave comment. By liking the specific comments you can vote for other ideas.
Thanks!
Hi
I am new to Solarwinds Orion so apologies if this has been answered before.
What I'm trying to do is set up a custom dashboard which can be an overview of our Linux servers (we also monitor a bunch of windows servers and network equipment but don't want them in this dashboard)
I would like to be able to display graphs etc which can show stats like:
Total network traffic across all Linux servers
A summary of CPU and memory usage - Show me servers which are using a high % of their memory or CPU etc
Show me any Linux servers which are nearly filling up their disk
All active alerts on only the Linux servers
There are others as well but that would be a good start, is something like this possible?
Cheers
Martin
I'm interested in building a report, or even generating a simple query with SDK / SWQL / SQL, that shows the total number of switchport with active link on them, once a day.
Meaning that if any port has a link on it at any time during a 24-hour period it would count as an active link.
I'd like this aggregated into a chart that shows a line graph of the active ports changing.
If it can generate the query more than once a day and show hourly active-port numbers changing, that would be even more interesting.
First off, I didn't find a canned report in SolarWinds NPM that can do this. Are you aware of one? If so, what's it called?
Second, have you already built a custom report that can do this? If so, would you share it with me, or share how you built it with me?
Last, do you know (or do you have a good idea) how to build a SWQL or SQL query that can display the total number of active ports on demand--or over time?
Swift Packets!
Rick Schroeder
Can someone point me to where, once exported, I can then re-import network maps into Network Atlas?
There is clearly an export function available, with various export options, yet look as I have, I see no option anywhere to import back into Network Atlas... ?
Use case for this for me is that I want to clear out a bunch of existing maps without deleting them and then have the option to add them back (import them) should I need to without having to recreate them all.
Thanks in advance,
Daniel
Hi team,
Has anyone created the report on Parent Child dependency, Following SQL query uses the ID and not name of the node.
SELECT TOP 1000 * FROM [dbo].[Dependencies]
Please help if anyone has done it.
Thanks
Prashant
We are installing Cisco 4110 within the next couple weeks. Any tricks or tips to get optimized performance out of SolarWinds with these?
Also .... What interface on the 4110 are you monitoring? Our rep told the chasis monitor will not provide any information but that was the only interface on the 4110 that we can get SW to communicate with.
Hello, we have a building power down scheduled and instead of emails firing off constantly - is there a way we can unmanage everything for like 12 hours ?
Working on an alert for response time using NPM v10.7. If I am correct, the warning and critical response time thresholds that I can set on the Node edit properties page are related to "current" response time. If my trigger condition is pointed to the variable Response Time and the Trigger must be sustained for 4 minutes (2 polls), why am I not seeing any alerts when I have a node that has been above the critical threshold for several polls in a row?
Both for our customers and our Support department it's very important to have a map, to be able to see the state of our network in one glance in a certain area. Say for example a sea-cable broke near Italy: one look at Italy on the map will show what sites are affected, regardless of whether they're grouped by supplier or whatever.
As far as I am aware, there are only two mapping tools for this purpose available in the NPM:
- Network Atlas
- Worldwide Map
Again as far as I'm aware, there is no way to automate the placement of nodes on the Network Atlas, since all documentation goes through the Network Atlas software tool. This makes this undesirable to use because our network is fairly large and new sites are added or cancelled on a daily basis, making it a real chore to keep this map up to date.
In the Worldwide Map this is, thankfully, possible and pretty easy. I have written a script that transfers(copies) nodes from our previous NMS to Solarwinds' and automatically pushes the node's geolocation (from custom properties) to the Worldwide Map. This was working wonderfully, until at some point the web interface just stopped working. The script kept running happily. It was just the web interface that become non-interactive. After some time I figured out that it was just the pages with a Worldwide map on it and that the Worldwide Map simply can't handle more than a 1000 nodes at one time (where is this even documented?).
Sidenode: 80% of our monitoring is ICMP only, so being able to sync custom properties with the Worldwide Map automatically would be grand.
Question 1:
Is there anything that I have overlooked that can provide such a worldwide map as we need it, for our 5000+ nodes and growing network, that doesn't require manual input? Our previous NMS (PRTG) had no issues with this whatsoever.
Once I found that out, I started investigating whether we could at least show a smaller scale map with just the nodes that are in a certain group on the Group Details page (which is better, but still not good enough). This is in fact possible, but only through a very ugly and cumbersome workaround. (As far as I know) you have to:
1) Create a new view for every group (every Worldwide Map instance seems to have a ResourceID that is linked to a viewID)
2) Edit the Worldwide Map for each view to only show the nodes in that group
3) Append the viewID to the default URL for that group and from now on use that to navigate to it.
Once more I have found no way to automate this process while there are currently ~500 groups to do this for and then we're not even talking about where to leave those ~500 new URLs that everone now has to use, while the intuitive way of navigating is by using the Group Summary.
Question 2:
Is there a way to flexibly change what is shown on the Worldwide map? Thinking beyond groups here, so using custom properties for this would would be nice: only show nodes for a certain supplier, end-customer, device-type, etc.
Hello
In iLO v4 available SNMP settings, and successfully polled Hardware Info and Hardware Health and other components.
But in iLO v3 available only SNMP Trap settings.
How can I configuring iLO or vCenter or Solarwinds to gather Hardware Info and Hardware Health from iLO v3?
Does anyone know if you can monitor HP ILO cards with Solarwinds?
I can't easily find info on this and don't see anywhere on the ilo web admin screen to configure a snmp community string.
Thanks,
Kevin
Those that have been part of the Thwack Community a while may be familiar with the long running Tell us your "Unknown" devices! thread which had been active since 2007. That thread had become too unwieldy, and most of the user submissions had been implemented many years ago. I recently reviewed each and every posting in that thread, verified what had been implemented in-product, and which ones had not so they could be included in a forthcoming release. With that done, it was time to lock that thread for good and start anew. This time, providing a bit more guidance along the way to ensure everyone is successful in providing the necessary information required to properly identify these devices.
Orion does its best to automatically identify and classify nodes as they're added to Orion. There are however, new device types and models released all the time. It's entirely possible you might be managing a device right now that Orion is unable to properly identify. You can find these easily by going to [Settings - Manage Nodes], changing the 'Group by:' option to 'Machine Type' and clicking on the 'Unknown' category. It's also helpful to add the 'Polling Method' column to the layout, as this thread pertains exclusively to SNMP managed nodes.
Any SNMP managed nodes listed under the 'Unknown' Machine Type category are prime candidates for submission to this thread. All that's required is that you provide the devices SNMP System Object Identifier (SysObjectID), as well as the Make & Model of the device associated with that SysObjectID. This post is an excellent example of the perfect submission.
I have yet to find a clearer definition for what the SysObjectID (System Object Identifier) is then the following excerpt which can typically be found written in virtually every vendor's MIB file verbatim.
Object Name: sysObjectID Object ID: 1.3.6.1.2.1.1.2.0 Object Syntax: OBJECT IDENTIFIER Object Access: read-only Object Status: mandatory Object Description: The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.
Essentially, it's a string of numbers in dotted notation that is (hopefully) unique to at least the manufacturer, and in most cases, to the specific make and model of the device being monitored. It's how we identify for example, that the device vendor is 'Cisco' and the model is a 'Nexus C7018'. All System Object ID's begin with '1.3.6.1.4.1' followed by a number which uniquely identifies the manufacturer. The numbers which then follow typically identify the specific model of the device.
If the device is already managed as a Node in Orion then you can locate the SysObjectID in the 'Node Details' resource as shown below, when viewing the node in the Orion web interface.
| Node Details | NET-SNMP |
|---|---|
 | Alternatively, you can use NET-SNMP to query the following SNMP OID to return the unique SysObjectID.
1.3.6.1.2.1.1.2.0
Below is an example of the 'snmpget' command line arguments which will return you the SysObjectID for the device.
snmpget -v2c -On -c public 10.199.5.103 1.3.6.1.2.1.1.2.0
The example above is executed against a device with the IP address of '10.199.5.103' using SNMPv2c, with the community string 'public'. Below is a screenshot of the resulting output from that command. The string of numbers and periods highlighted in yellow below is this device's unique SysObjectID.
|
Linux hosts, virtual appliances, and even some network equipment built on Linux, FreeBSD, etc. are often identified as 'NET-SNMP'. This is because the SNMP Daemon running on those hosts is, you guessed it, NET-SNMP. Unfortunately, these vendors for some reason, have chosen not to implement their own unique SysObjectID, and instead kept the default SysObjectID '1.3.6.1.4.1.8072.3.2.10' which is designated for NET-SNMP. If you have a device such as this, fret not. There are a few options available to you if you'd like these devices to be properly identified by their appropriate vendor's make & model within Orion.
The easiest solution would be to install the Orion Linux Agent on the device which is reporting itself to be 'NET-SNMP'. The Linux Agent does not rely upon SNMP to identify the machine type or vendor. Instead, the Agent will report the Vendor as 'Linux' and the 'Machine Type' as the Linux distribution running on the device as depicted in the screenshots below.
| Red Hat | Citrix XenServer |
|---|---|
 |  |
Another approach is to customize NET-SNMP and Orion to properly reflect the Vendor and Machine Type. Simply following the steps outlined by adatole's post entitled No More Net-SNMP Nodes. This method uses a script osname.sh which is executed when a particular OID is is queried. Next, you would create a custom Device Poller to query that newly created OID and populate the Machine Type value in Orion for that device.
If you find it more fun to follow along, you can watch adatole walk you through the entire process in the following video.
While it would be nice if that's how it worked, unfortunately many (or most) vendors don't include this information within their MIB files. MIB files include a listing of all possible OIDs which could be polled across a wide variety of different devices (typically an entire product family), but it doesn't include the values which are returned by the devices (Enums notwithstanding). For that reason we need users, such as yourself, to post the SysObjectID's in this thread, along with the device vendor and model information so it can be included in our database.
If you'd still like your device's MIB file included in the Orion MIB database, for use with Network Performance Monitor's Universal Device Poller, or the Orion Platform's SNMP Trap Receiver, simply follow the steps outlined in KB article at the link below. The latest version of the MIB database, containing your submissions, can always be downloaded from within the Customer Portal.
Hello,
We've just installed a couple of Acculab ApplanX IP Gateway devices as part of a SIP deployment, and I'd like to monitor them using NPM. I've done a couple of searches and can't find a UnDP for them, but Acculab do make the MIB's available via the device management console. I've pasted the MIB's below.
Or, if anyone has a UnDP for these devices that would be helpful too?
For info, when I add them to NPM at the moment they just identify themselves as machine type "net-snmp - Linux"
AculabMIB.txt
ACULAB-ROOT-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises, Counter32, OBJECT-TYPE, MODULE-IDENTITY
FROM SNMPv2-SMI
DisplayString
FROM SNMPv2-TC;
Aculab MODULE-IDENTITY
LAST-UPDATED "200801291750Z"
ORGANIZATION "Aculab plc"
CONTACT-INFO "www.aculab.com"
DESCRIPTION "Aculab Root MIB"
::= { enterprises 11269 }
prosodyx OBJECT-IDENTITY
STATUS current
DESCRIPTION "ProsodyX Hardware"
::= { Aculab 1 }
GroomerII OBJECT-IDENTITY
STATUS current
DESCRIPTION "Groomer"
::= { Aculab 4 }
ApplianX OBJECT-IDENTITY
STATUS current
DESCRIPTION "ApplianX"
::= { Aculab 5 }
END
AculabApplianXMIB.txt
-- Aculab plc ApplianX MIB
-- Version 1.0
-- This is the main MIB for Aculab ApplianX
-- ISDN, CAS, ISUP, protocol conversion, VoIP media gateway product.
--
-- This document is Copyright (c) 2008 Aculab plc.
ACULAB-APPLIANCE-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises, OBJECT-TYPE, Integer32, MODULE-IDENTITY
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString
FROM SNMPv2-TC
Aculab, ApplianX
FROM ACULAB-ROOT-MIB;
aculabApplianX MODULE-IDENTITY
LAST-UPDATED "201311271300Z"
ORGANIZATION "Aculab plc"
CONTACT-INFO "www.aculab.com"
DESCRIPTION "MIB for ApplianX SNMPv2"
::= { ApplianX 1 }
aculabApplianXStatus OBJECT-IDENTITY
STATUS current
-- ACCESS not-accessible
DESCRIPTION "Generic ApplianX Status"
::= { aculabApplianX 1 }
applianXDefs OBJECT-IDENTITY
STATUS current
DESCRIPTION "Definition point for generic ApplianX types and notifications."
::= { aculabApplianXStatus 0 }
applianXTypes OBJECT-IDENTITY
STATUS current
DESCRIPTION "ApplianX Types"
::= { applianXDefs 1 }
applianXNotifications OBJECT-IDENTITY
STATUS current
DESCRIPTION "Definition point for generic ApplianX types and notifications."
::= { applianXDefs 2 }
applianXName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION
"The name that has been applied to the ApplianX"
::= { aculabApplianXStatus 1 }
applianXSerialNumber OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION
"A unique number that identifies the ApplianX"
::= { aculabApplianXStatus 2 }
applianXSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION
"The version of the software running on the device"
::= { aculabApplianXStatus 3 }
applianXSoftwareBuildDate OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION
"The build date of the software running on the device"
::= { aculabApplianXStatus 4 }
applianXUptime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS current
DESCRIPTION
"the uptime of the ApplianX in 100/ths of a second"
::= { aculabApplianXStatus 5 }
--
-- Hardware information
--
applianXHWTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplianXHWEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "List of hardware components on this card"
::= { aculabApplianXStatus 6 }
applianXHWEntry OBJECT-TYPE
SYNTAX ApplianXHWEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Hardware components"
INDEX { applianXHWDevice }
::= { applianXHWTable 1 }
ApplianXHWEntry ::= SEQUENCE {
applianXHWDevice INTEGER,
applianXHWSerial DisplayString,
applianXHWPartNo DisplayString,
applianXHWTemp1 INTEGER,
applianXHWTemp2 INTEGER,
applianXHW33vVoltage INTEGER,
applianXHW5vVoltage INTEGER
}
applianXHWDevice OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Device index"
::= { applianXHWEntry 1 }
applianXHWSerial OBJECT-TYPE
SYNTAX DisplayString (SIZE(1..30))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Device serial number"
::= { applianXHWEntry 2 }
applianXHWPartNo OBJECT-TYPE
SYNTAX DisplayString (SIZE(1..20))
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Device part number"
::= { applianXHWEntry 3 }
applianXHWTemp1 OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Temperature 1"
::= { applianXHWEntry 4 }
applianXHWTemp2 OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Temperature 2"
::= { applianXHWEntry 5 }
applianXHW33vVoltage OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "3.3v voltage being received by device"
::= { applianXHWEntry 6 }
applianXHW5vVoltage OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "5v voltage being received by device"
::= { applianXHWEntry 7 }
--
-- Trunk information
--
applianXTrunkTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplianXTrunkEntryS
ACCESS not-accessible
STATUS current
DESCRIPTION "List of trunks on this card"
::= { aculabApplianXStatus 7 }
applianXTrunkEntry OBJECT-TYPE
SYNTAX ApplianXTrunkEntryS
ACCESS not-accessible
STATUS current
DESCRIPTION "Information about a trunk"
INDEX { applianXTrunkIx }
::= { applianXTrunkTable 1 }
ApplianXTrunkEntryS ::= SEQUENCE {
applianXTrunkIx INTEGER,
applianXTrunkProtocol DisplayString,
applianXLayer1bipvios INTEGER,
applianXLayer1faserrs INTEGER,
applianXLayer1sliperrs INTEGER,
applianXLayer1nos INTEGER,
applianXLayer1ais INTEGER,
applianXLayer1los INTEGER,
applianXLayer1rra INTEGER,
applianXLayer1tra INTEGER,
applianXLayer1rma INTEGER,
applianXLayer1tma INTEGER,
applianXLayer1usr INTEGER,
applianXLayer2State INTEGER
}
applianXTrunkIx OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Trunk index"
::= { applianXTrunkEntry 1 }
applianXTrunkProtocol OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION
"Protocol running on this trunk"
::= { applianXTrunkEntry 2 }
applianXLayer1bipvios OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "The number of frames that include at least 1 bit error in the Frame Alignment Signal"
::= { applianXTrunkEntry 3 }
applianXLayer1faserrs OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "The number of frames that include at least 1 bit error in the Frame Alignment Signal"
::= { applianXTrunkEntry 4 }
applianXLayer1sliperrs OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "The number of received frame slips in the incoming G703 signal"
::= { applianXTrunkEntry 5 }
applianXLayer1nos OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that this trunk is not receiving a signal"
::= { applianXTrunkEntry 6 }
applianXLayer1ais OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that this trunk is receiving an Alarm Indication from the far end"
::= { applianXTrunkEntry 7 }
applianXLayer1los OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that this trunk has lost synchronisation"
::= { applianXTrunkEntry 8 }
applianXLayer1rra OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that the far end is sending a remote alarm to this trunk"
::= { applianXTrunkEntry 9 }
applianXLayer1tra OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that a remote alarm is being transmitted by this trunk"
::= { applianXTrunkEntry 10 }
applianXLayer1rma OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that the far end is sending a multiframe alarm to this trunk"
::= { applianXTrunkEntry 11 }
applianXLayer1tma OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Indicates that a multiframe alarm is being transmitted by this trunk"
::= { applianXTrunkEntry 12 }
applianXLayer1usr OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Provides fault conditions described in CCITT I431"
::= { applianXTrunkEntry 13 }
applianXLayer2State OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "Layer 2 state for this trunk "
::= { applianXTrunkEntry 14 }
--
-- Network interfaces
--
applianXNetworkIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplianXNetworkIfEntry
ACCESS not-accessible
STATUS current
DESCRIPTION "State of the specified media interface"
::= { aculabApplianXStatus 8 }
applianXNetworkIfEntry OBJECT-TYPE
SYNTAX ApplianXNetworkIfEntry
ACCESS not-accessible
STATUS current
DESCRIPTION "The status of a single network interface"
INDEX { applianXNetworkIfIx }
::= { applianXNetworkIfTable 1 }
ApplianXNetworkIfEntry ::= SEQUENCE {
applianXNetworkIfIx INTEGER,
applianXNetworkIfConnectionState INTEGER,
applianXNetworkIfSpeed INTEGER,
applianXNetworkIfPacketsReceived INTEGER,
applianXNetworkIfPacketsSent INTEGER
}
applianXNetworkIfIx OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Interface index"
::= { applianXNetworkIfEntry 1 }
applianXNetworkIfConnectionState OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "State of the interface"
::= { applianXNetworkIfEntry 2 }
applianXNetworkIfSpeed OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Speed of the connection"
::= { applianXNetworkIfEntry 3 }
applianXNetworkIfPacketsReceived OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Number of packets received on this interface"
::= { applianXNetworkIfEntry 4 }
applianXNetworkIfPacketsSent OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Number of packets sent on this interface"
::= { applianXNetworkIfEntry 5 }
--
-- Notifications
--
applianXAlarmIx OBJECT-TYPE
SYNTAX Integer32
ACCESS read-only
STATUS current
DESCRIPTION "The resource that has raised the notification"
::= { applianXTypes 1 }
applianXAlarmStatus OBJECT-TYPE
SYNTAX INTEGER {
down(0),
up(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "The status of the resource"
::= { applianXTypes 2 }
applianXClockSource OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION "The current clock source for the applianX"
::= { applianXTypes 3 }
applianXClockStatus OBJECT-TYPE
SYNTAX INTEGER {
bad(0),
good(1)
}
ACCESS read-only
STATUS current
DESCRIPTION "The current state of the clock"
::= { applianXTypes 4 }
applianXSystemNotificationCategory OBJECT-TYPE
SYNTAX INTEGER {
general(0), -- notifications that don't fall into another category
configuration(1), -- notifications relating to configuration loading
system(2), -- notifications relating to system functionality (starting/stopping/etc)
webInterface(3) -- notifications relating to the web interface
}
ACCESS read-only
STATUS current
DESCRIPTION "The category of the event being reported"
::= { applianXTypes 5 }
applianXSystemNotificationSeverity OBJECT-TYPE
SYNTAX INTEGER {
informational(0), -- this notification is for information only
warning(1), -- this notification is a warning
error(2), -- this notification indicates that an error has occurred. Call traffic may be affected.
critical(3) -- this notification indicates that a critical error has occurred. Call traffic is definitely affected.
}
ACCESS read-only
STATUS current
DESCRIPTION "The severity of the event being reported"
::= { applianXTypes 6 }
applianXSystemNotificationEvent OBJECT-TYPE
SYNTAX INTEGER {
gatewayInitialised(0), -- indicates that the gateway is initialising
gatewayTerminated(1), -- indicates that the gateway has terminated
gatewayRunning(2), -- indicates that the gateway is able to handle calls
gatewayStopped(3), -- indicates that the gateway is not able to handle calls
configurationLoadStarted(20), -- the gateway has begun to load a configuration
configurationLoadSucceeded(21), -- the gateway has finished loading a configuration
configurationLoadFailed(22), -- the gateway has failed to load a configuration
configurationNotSpecified(23), -- There is no configuration to be loaded
protocolFirmwareDownloadSucceeded(40), -- call control firmware has been downloaded
protocolFirmwareDownloadFailed(41), -- call control firmware has failed to be downloaded
dspFirmwareDownloadSucceeded(60), -- dsp firmware has been downloaded
dspFirmwareDownloadFailed(61), -- dsp firmware has failed to download
webInterfaceLoginSuccessful(80), -- a user has logged into the web interface
webInterfaceLoginFailed(81), -- a user has failed to log into the web interface
monitoredProcessRunning(100),
monitoredProcessStopped(101),
monitoredProcessTimedOut(102),
monitoredProcessFailed(103),
processDumpedCore(120), -- a process has dumped core
tlsCertificateNearExpiry(130), -- one or more TLS certificates are near to expiry
tlsCertificateExpired(131), -- one or more TLS certificates have expired
httpsCertificateNearExpiry(132), -- the HTTPS certificate is near to expiry
httpsCertificateExpired(133), -- the HTTPS certificate has expired
modeStandard(134), -- the gateway is in standard mode of operations
modeSurvivability(135), -- the gateway is in survivability mode of operations
barredNumberDialed(140) -- An attempt was made to dial a barred number
}
ACCESS read-only
STATUS current
DESCRIPTION "The type of event being reported"
::= { applianXTypes 7 }
applianXSystemNotificationMessage OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS current
DESCRIPTION "Descriptive text for the event being reported"
::= { applianXTypes 8 }
applianXSystemNotificationIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION "Index of resource raising trap (not all events provide a meaningful value for this item"
::= { applianXTypes 9 }
applianXTrunkLayer1StatusNotification NOTIFICATION-TYPE
OBJECTS { applianXAlarmIx, applianXAlarmStatus }
STATUS current
DESCRIPTION "This trap is generated when layer 1 on a trunk changes state"
::= { applianXNotifications 1 }
applianXNetworkIfStatusNotification NOTIFICATION-TYPE
OBJECTS { applianXAlarmIx, applianXAlarmStatus }
STATUS current
DESCRIPTION "This trap is generated when a media interface changes state"
::= { applianXNotifications 2 }
applianXSystemNotification NOTIFICATION-TYPE
OBJECTS {
applianXSystemNotificationCategory,
applianXSystemNotificationSeverity,
applianXSystemNotificationEvent,
applianXSystemNotificationMessage,
applianXSystemNotificationIndex
}
STATUS current
DESCRIPTION "This trap indicates that a system event has occurred."
::= { applianXNotifications 3 }
applianXTrunkLayer2StatusNotification NOTIFICATION-TYPE
OBJECTS { applianXAlarmIx, applianXAlarmStatus }
STATUS current
DESCRIPTION "This trap is generated when layer 2 on a trunk changes state"
::= { applianXNotifications 4 }
--
-- Gateway product specific objects
--
aculabApplianXGateway OBJECT-IDENTITY
STATUS current
DESCRIPTION "Gateway status"
::= { aculabApplianX 2 }
applianXRegistrations OBJECT-TYPE
SYNTAX Integer32
ACCESS read-only
STATUS current
DESCRIPTION
"The number of successful registration requests processed by the server"
::= { aculabApplianXGateway 1 }
applianXAuthType OBJECT-TYPE
SYNTAX INTEGER {
none(1),
MD5(2),
Radius(3),
RadiusDB(4)
}
ACCESS read-only
STATUS current
DESCRIPTION
"The Type of Authorisation Scheme in use by the server"
::= { aculabApplianXGateway 2 }
applianXInCallCount OBJECT-TYPE
SYNTAX Integer32
ACCESS read-only
STATUS current
DESCRIPTION
"The number of successful incoming calls handled by the server"
::= { aculabApplianXGateway 3 }
applianXOutCallCount OBJECT-TYPE
SYNTAX Integer32
ACCESS read-only
STATUS current
DESCRIPTION
"The number of successful outgoing calls made by the server"
::= { aculabApplianXGateway 4 }
applianXUnRouteableCall OBJECT-TYPE
SYNTAX Integer32
ACCESS read-only
STATUS current
DESCRIPTION
"The number of unroutable calls handled by the server"
::= { aculabApplianXGateway 5 }
END
Do you have a need to detect rogue APs connected to your network?
