Using SNMP to monitor Nexus 7000 Series Supervisor Module

Hello,
I got a Nexus 7000 supervisor module recently, I met a SNMP problem for this module
I would like to know which specific OIDs to use to monitor the following using SNMP on a Nexus 7000 supervisor module:
- Port status
- CPU total utilization
- Power Supply status
- Chassis Fan status
etc.
The Nexus is quite different from other Cisco devices - any help will be appreciated!

hope help, and
port status OID is ifOperStatus
CPU total utilization OID is 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifDescr.83886080
.1.3.6.1.2.1.2.2.1.2.83886080 = STRING: mgmt0
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifOperStatus.83886080
.1.3.6.1.2.1.2.2.1.8.83886080 = INTEGER: up(1)
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
.1.3.6.1.4.1.9.9.109.1.1.1.1.6.1 = Gauge32: 21
[root@NET-MONITOR-1 ~]#

Similar Messages

Nexus 7000's Supervisor Module cannot boot up

Hi all,
I have one of redundant supervisor module in Nexus 7010 that cannot boot up. I tried to do recovery from loader but it cannot boot the kickstart image and reboot again. The log is :
loader> set ip 192.168.253.10 255.255.255.0
Correct - ip addr is 192.168.253.10, mask is 255.255.255.0
Found Intel 82546GB [2:9.0] at 0xe040, ROM address 0xf980
Probing...[Intel 82546GB]
Management interface
Link UP in 1000/full mode
Ethernet addr: C0:62:6B:AD:35:80
Address: 192.168.253.10
Netmask: 255.255.255.0
Server: 0.0.0.0
Gateway: 0.0.0.0
loader> boot tftp://192.168.253.43/n7000-s1-kickstart.5.1.5.bin
Address: 192.168.253.10
Netmask: 255.255.255.0
Server: 192.168.253.43
Gateway: 0.0.0.0
Filesystem type is tftp, using whole disk
Booting: /n7000-s1-kickstart.5.1.5.bin console=ttyS0,9600n8nn quiet loader_ver=
"3.22.0"....
....................Image verification OK
INIT: owner_pc=c03a7956 held lock for 5010 msec
NX7 SUP Ver 3.22.0
Serial Port Parameters from CMOS
PMCON_1: 0x200
PMCON_2: 0x0
PMCON_3: 0x3a
PM1_STS: 0x101
Performing Memory Detection and Testing
Total mem found : 4096 MB
Performing memory test... Passed.
NumCpus = 2.
Status 61: PCI DEVICES Enumeration Started
Status 62: PCI DEVICES Enumeration Ended
Status 9F: Dispatching Drivers
Status 9E: IOFPGA Found
Status 9A: Booting From Primary ROM
Status 98: Found Cisco IDE
Status 98: Found Cisco IDE
Status 98: Found Cisco IDE
Status 90: Loading Boot Loader
Reset Reason Registers: 0x0 0x8
              GNU GRUB version 0.97
                Loader Version 3.22.0
Netbooting via EOBC ...
Found Intel 82571EB [4:0.1] at 0xc000, ROM address 0x0000
Probing...[Intel 82571EB]
Sup-to-sup interface
Ethernet addr: 00:00:00:00:05:00
Address: 127.1.2.5
Netmask: 255.255.0.0
Server: 127.1.1.6
Gateway: 0.0.0.0
Address: 127.1.2.5
Netmask: 255.255.0.0
Server: 127.1.1.6
Gateway: 0.0.0.0
Filesystem type is tftp, using whole disk
Booting: /img-sync/curr-ks.img console=ttyS0,9600n8nn isanimg=tftp://127.1.1.6/
img-sync/curr-isan.img quiet loader_ver="3.22.0"....
....................Image verification OK
INIT: version 2
Does anybody have an idea?
Thanks.

That makes sense.
1. Restore the default VDC config.
2. Create your second VDC.
3. Restore the second VDC config.
Don't forget to have a backup of any license files that you may have purchased, for example MPLS.

Use SNMP to monitor the power supply status of stacked switches

Does anybody know how to use SNMP to monitor the status of the internal power supplies of a group of stacked Cisco 3750 switches?
The switch stack has three 3750-48PS-E switches inter-connected by Cisco StackWise cable. IOS ver 12.1(19)EAlc. A single IP address is used to identify the switch stack. Every time I poll the OID chassisPs1Status (1.3.6.1.4.1.9.5.1.2.4.0 in CISCO-STACK-MIB), I only got the status for the Master switch of the switch stack. Is there any way to poll the power supply status of other switches in the switch stack?
Thanks a lot!

Sorry to refresh such an old topic - but I am stuck with exactly this: Monitoring power supplies of a stacked Cisco Catalyst 3750-E.
I'm using the exact same OID's as described, but the problem is, the information shown on the SNMP output is not correct.
This morning, a power supply of the first switch failed and switched to RPS. Here the information I got on SNMP:
snmpwalk -v 2c -c public 192.168.1.50 1.3.6.1.4.1.9.9.13.1
SNMPv2-SMI::enterprises.9.9.13.1.1.0 = INTEGER: 13
SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.1006 = STRING: "SW#1, Sensor#1, GREEN "
SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.2006 = STRING: "SW#2, Sensor#1, GREEN "
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.1006 = Gauge32: 41
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.2006 = Gauge32: 40
SNMPv2-SMI::enterprises.9.9.13.1.3.1.4.1006 = INTEGER: 59
SNMPv2-SMI::enterprises.9.9.13.1.3.1.4.2006 = INTEGER: 59
SNMPv2-SMI::enterprises.9.9.13.1.3.1.5.1006 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.13.1.3.1.5.2006 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.13.1.3.1.6.1006 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.3.1.6.2006 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.4.1.2.1060 = STRING: "Switch#1, Fan#1"
SNMPv2-SMI::enterprises.9.9.13.1.4.1.2.2059 = STRING: "Switch#2, Fan#1"
SNMPv2-SMI::enterprises.9.9.13.1.4.1.3.1060 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.4.1.3.2059 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1059 = STRING: "Sw1, PS1 Normal, RPS NotExist"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2060 = STRING: "Sw2, PS1 Normal, RPS NotExist"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.1059 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.2060 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.1059 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.2060 = INTEGER: 2
As you see, both PS1 (for both switches) are appearing normal. It doesn't even recognize RPS:
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1059 = STRING: "Sw1, PS1 Normal, RPS NotExist"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2060 = STRING: "Sw2, PS1 Normal, RPS NotExist"
The first switch's power supply died and now the cable is disconnected. LED's of the power supply are out. And still: The switch happily announces by SNMP it's power supplies are up.
Is this a known bug? If yes, has it been fixed?
Model WS-C3750E-48TD
Firmware 12.2(37)SE1
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}

Infrastructure Nexus 7000 Series or 7700 Series.

Dear,
I have a big question, now the data center infrastructure and equipment changes continuously creating new top models for processing named Nexus.
I can consider an architecture with Nexus 7K, 5K and 2K for a datacenter or should jump and use Nexus 7700 Series and 9K leveraging its capabilities and new generation?
I've clear demand and size of the data center but what is the best option.
Someone could give me your recommendations.
Best Regards.

The answer is driven by your business needs.
Install 9Ks if you need to leverage their SDN and ACI capabilities. You also need to remember that the N9Ks are relatively new to the market in comparison to the N7Ks and so their features are still maturing.
However if you don't need this functionality then personally I would install the N77Ks given that they are the newest generation of the N7K switch family.
Whether you also deploy 5Ks and 2Ks depends largely on your overall Top of Rack switch design.
If you choose a middle of row or end of row switch design then the need for these types of switches diminishes. This is based on the assumption that you don't need to leverage the N5Ks fibre channel capabilities.
Don't forget to rate all helpful posts.

Using SNMP to monitor DMVPN NHRP

Are there any SNMP OIDs for monitoring dynamic DMVPN NHRP entries? I'd like to poll my hub router for a list of active DMVPN spokes, and NHRP seems like the best thing to check, but I can't find any MIBs for NHRP outside of the Frame Relay context.
Thanks!
-Mason

Hi
I use these OID for my DMVPN query.
***HUB***
Active IKE sessions (count)
get .1.3.6.1.4.1.9.9.171.1.2.1.1.0
Active IPSec sessions (count)
get .1.3.6.1.4.1.9.9.171.1.3.1.1.0
IKE Peer's IP address (list)
walk .1.3.6.1.4.1.9.9.171.1.2.2.1.7.0
***SPOKE***
IKE History (ID)
walk .1.3.6.1.4.1.9.9.171.1.4.2.1.1.8
IKE History (reason based on ID)
walk .1.3.6.1.4.1.9.9.171.1.5.2.1.1.2
I don't know if it's exactly what you want. But if it's not, you can walk the cisco mib 1.3.6.1.4.1.9 in a text file and grab what you want. It's like this that I've found my OID
Enjoy :)

Nexus 7000 single supervisor replacement

Does anyone have a good process for replacing a N7k single supervisor setup if say the supervisor died and had to be replaced. With N7k's and VDC's this becomes more problematic as the global vdc and other vdc's use separate config files . What is the easiest way to get everything back on to the new supervisor ? I have searched all over and can't find a decent process on how this might be done . We do have the configs on a SCP server . It's not as easy as the IOS boxes where you have a single config file to get back on . thanks...

Hi Glen,
I think you could use the below as a useful guide.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_hig_book/n7k_replacing.html#pgfId-1410535
You could copy the current configuration of all vdc to a usb drive and later restore them back to new sup.
copy running-config usb1:configuration_file_name vdc-all
and later copy the config file back to running config on new sup. Kindly go through the above link to understand better.
Hope this helps you.
Thanks,
Madhu

Frame generated by Nexus 7000 contains unexpected trailer when using GRE

I have observed some unexpected behaviour on a Nexus 7000 running 6.1(2) in respect of the Ethernet II frame generated when the Nexus 7000 is a GRE Tunnel endpoint.
The device receiving the Frame is discarding it and I waiting for the vendor to confirm the reason for this discard. However in case the reason is due to the Ethernet frame being "unusual" I am curious if any one else has come across this.
To generate the Frame I perform a ping (on a workstation) which the Nexus 7000 in encapsulating in a GRE tunnel. Using Wireshark on the Nexus 7000 egress interface I observed that the Frame contains the following protocols as expected; ETH:IP:GRE:IP:ICMP:data
When I issue the command "ping -l 1" on the workstation the Frame details from Wireshark are:
Frame 84 bytes on wire
Total IP payload = 53 bytes
Outer IP header (20 bytes)
GRE ( 4 bytes)
Inner IP header (20 bytes)
ICMP (header 8 bytes payload 1 byte)
Ethernet Trailer length = 17 bytes
What is curious about this Frame is that;
a) No Ethernet Trailer is needed as the IP payload exceeds 46 bytes
b) The amount of padding applied is what would be needed if the Inner IP datagram were encapsulated directly in an Ethernet II Frame. The Inner ip datagram is 29 bytes octets and hence padding needed = 46 - 29 = 17.
By doing ping sweep from length 1 to 18 the observed padding was;
1,17
2,16
3,15
17,1
18,0
So it would appear that the Nexus is adding padding to the Ethernet frame as though it were containing the pre GRE payload only.

What module are you using?
Ron

Ask the Expert: Basic Introduction and Troubleshooting on Cisco Nexus 7000 NX-OS Virtual Device Context

With Vignesh R. P.
Welcome to the Cisco Support Community Ask the Expert conversation.This is an opportunity to learn and ask questions of Cisco expert Vignesh R. P. about the Cisco® Nexus 7000 Series Switches and support for the Cisco NX-OS Software platform .
The Cisco® Nexus 7000 Series Switches introduce support for the Cisco NX-OS Software platform, a new class of operating system designed for data centers. Based on the Cisco MDS 9000 SAN-OS platform, Cisco NX-OS introduces support for virtual device contexts (VDCs), which allows the switches to be virtualized at the device level. Each configured VDC presents itself as a unique device to connected users within the framework of that physical switch. The VDC runs as a separate logical entity within the switch, maintaining its own unique set of running software processes, having its own configuration, and being managed by a separate administrator.
Vignesh R. P. is a customer support engineer in the Cisco High Touch Technical Support center in Bangalore, India, supporting Cisco's major service provider customers in routing and MPLS technologies. His areas of expertise include routing, switching, and MPLS. Previously at Cisco he worked as a network consulting engineer for enterprise customers. He has been in the networking industry for 8 years and holds CCIE certification in the Routing & Switching and Service Provider tracks.
Remember to use the rating system to let Vignesh know if you have received an adequate response.
Vignesh might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community discussion forum shortly after the event. This event lasts through through January 18, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

Hi Vignesh
Is there is any limitation to connect a N2K directly to the N7K?
if i have a an F2 card 10G and another F2 card 1G and i want to creat 3 VDC'S
VDC1=DC-Core
VDC2=Aggregation
VDC3=Campus core
do we need to add a link between the different VDC's
thanks

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Nexus 7000 route leak from GRT (default VRF) to other VRF's

Hello
We have a Nexus 7000 infrastructure whereby we have had multiple VDC's and VRF's deployed. A requirement has now come about whereby one of these VRF's needs to be able to see our GRT (default VRF) so we need to leak the GRT routes into the VRF and vice versa.
I have been doing a lot of reading and I am happy with the how this works with inter-VRF route leaking but I seem to missing a few things in respect of how this works with the GRT.
I have also read on another forum that this is not supported. See link below.
https://supportforums.cisco.com/document/133711/vrf-configuration-and-verification-nexus-7000
Does anyone have experience of this? I can also see how this works in IOS and I have GNS3 and got this working.
We use BGP currently so we are able to use MP-BGP if required.
Any help would be very useful.

Hi,
In Table 14 of the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide the verified limit is specified as 1000 per system i.e., across all VDCs for NX-OS release 5.2, 6.0 and 6.1.
There is a footnote associated with this number which states:
With each new VDC configured, the number of configurable VRFs per system is reduced by two as each VDC has a default VRF and management VRFs that are not removable. For example, with 8 configured VDCs on Cisco NX-OS Release 5.2, you can configure up to 984 VRFs per system (either all in one VDC or across VDCs).
Regards

Broadcom LiveLink : Receiving MAC flaps with Cisco Nexus 7000

We are migrating from using two Nortel 8600's running VRRP at the distribution to Cisco Nexus 7K's using HSRP. So we have a server connected to two 3750G switches which then connect to the Nexi (previously the 8600's). As soon as we connected the 3750's to the Nexus and moved the gateway to Nexus, LiveLink forces all the servers to alternate traffic between NIC1 and NIC2.
Since LiveLink is a teaming application, it uses virtual mac for nic1 and nic2, but the virtual mac associated with the IP address moves to the active link.
LiveLink is used to check the availability of the gateway by polling the gateway out of each interface using an ARP request.
The problem does not exhibit itself in our Cisco VSS environment, and with Nortel's VRRP. I tried running VRRP on the Nexus but no joy.
Anyone know of a bug that could cause this issue?

Unfortunately we have LiveLink enabled on most of our Windows servers in our data centers. One of my colleagues sent me this bug issue. I'm not sure if this is the cause, but it's worth trying. We will update the NxOs (currently on 5.1.1) next week and see if that fixes the problem.
•CSCtl85080
Symptom: Incomplete Address Resolution Protocol (ARP) entries are observed on a Cisco Nexus 7000 Series switch, along with partial packet loss and a memory leak.
Conditions: This symptom might be seen when ARP packets have a nonstandard size (that is, greater than 64 bytes).
Workaround: This issue is resolved in 5.1.3.

SNMP Probe monitor query

Hi ,
I have created SNMP Probe based monitor to check the Total RAM free on certain Network devices.
I have total 16GB RAM space and i want to alert if lesser than 3 GB of Total RAM. I had configured /DataItem/SnmpVarBinds/SnmpVarBind[1]/Value lesser than 3467826 to be critical and alert. The other condition is /DataItem/SnmpVarBinds/SnmpVarBind[1]/Value
greater than 3467826 to be healthy.
Once configured i am getting alerts for higher values like 19458676. could someone please help me with this scenario and correct me if i am wrong.
Jesty Sam

Why you use SNMP to monitor RAM, you can create custom monitor for RAM between 2 value min. and Max.
SNMP is the most commonly used method mainly because it is easy to set up and requires minimal bandwidth and CPU cycles. If your network devices support SNMP and/or if you want to monitor large networks with several hundred or thousands of sensors, we recommend
you to start with SNMP. Besides network usage monitoring, another well-known feature of SNMP is the ability to also watch other network parameters such as CPU load, disk usage, temperature, as well as monitoring many other readings, depending on the queried
device.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
Technical | Twitter:
Mai Ali

Possible overflow for jvmRuntimeHeapSizeCurrent using SNMP?

I'm trying to use SNMP to monitor a managed server (WebLogic 8.1 SP4) and am trying to get the value for the attribute jvmRuntimeHeapSizeCurrent (which has the OID 1.3.6.1.4.1.140.625.340.1.30). The server is configured to start with 2 GB of RAM. The returned value for that attribute is -2147483648 which I think indicates an overflow. The SNMP data type for that OID is INTEGER.
Am I running into a bug? Or does that negative integer indicate something else? Since an INTEGER type cannot have a value more than 2147483647 (approx 1.99 GB), what might be the returned values for Heap sizes greater than 2 GB?
If I should be asking this question elsewhere please let me know where.
Thanks for any help on this.
Kartik

Hi,
I Found CR189563.
It seems the value returned in being stored in int variable which should be a long variable. I have explained that in CR. Engineering is evaluating it and right now it's marked for next release. I will keep you updated regarding any development on this CR.
You can get other statistics using other oid
http://e-docs.bea.com/wls/docs61/snmp/snmpruntime.html#1031510
Prasanna Yalam

Dell Inspiron 7000 series dual monitor issue

Today tried to connect Dell Inspiron 7437 to external monitor using HDMI cord; it did not work. I changed setting to external monitor only and now cannot get an image on laptop screen or external monitor when HDMI cord is connected. Tried to restart computer; still goes to blank screen as soon as I plug in HDMI.
1. How to a return to default setting for laptop display so it's only set to laptop?
2. Is it possible to connect inspiron 7000 to external monitor with hdmi?
Thank you

Hello,
Yes, it is possible to connect the Inspiron 7000 series to an external monitor using an HDMI cable. Normally you can control how the video is displayed by using the <FN>+<F8> key combination. Normally your options are LCD only, duplicate display on the LCD & the external monitor, or just display on the external monitor (projector mode). Try that key combination to see if you can toggle between the available displays.
One thing you also might want to check to see is if that monitor is set to a resolution that your system cannot handle. Here is a link to the product support pages for the Inspiron 7437, and you will find user manuals on the page that will help explain which resolutions your video card can handle. You may need to set your monitor back to default settings (see your user manual for that monitor for details) and that should enable your system to send video to it.
Let me know if any of this helps or if you have additional questions.
Todd

Nexus 7000 supervisor replacement

I'm trying to get my head around how to replace a supervisor module on a nexus 7000 with a single supervisor. The setup has the default vdc and one other defined. So if a sup was faulty what is the best way to handle this? I have the default vdc config and the other vdc on a tftpboot server. Whats the easiest and fastest way to hand this . In the default vdc add address and copy the default vdc config and then when that's in copy the other vdc config file. Just used to IOS where you normally had a single file and you got the box on the air enough to copy the config file into startup and reloaded . Hope this makes sense. Tried to read some of the docs but it's still not clear what exactly needs to be done. Thanks for any help...

That makes sense.
1. Restore the default VDC config.
2. Create your second VDC.
3. Restore the second VDC config.
Don't forget to have a backup of any license files that you may have purchased, for example MPLS.

Using SNMP to monitor Nexus 7000 Series Supervisor Module

Similar Messages

Maybe you are looking for