Sponsored Content
Full Discussion: LPAR RMC state for DLPAR
Operating Systems AIX LPAR RMC state for DLPAR Post 303043017 by Phat on Thursday 16th of January 2020 12:01:11 AM
Old 01-16-2020
LPAR RMC state for DLPAR

Hello,

I have checked the state of rmc on the HMC as below:
Code:
HMC1:~> lssyscfg -r lpar -m Server-xxx -F lpar_id,state,rmc_state,rmc_ipaddr,os_version,dlpar_mem_capable,dlpar_proc_capable,dlpar_io_capable --filter "lpar_ids=4"
4,Running,inactive,10.176.x.x,VIOS 2.2.6.51,0,0,0

HMC1:~> lssyscfg -r lpar -m Server-xxx -F lpar_id,state,rmc_state,rmc_ipaddr,os_version,dlpar_mem_capable,dlpar_proc_capable,dlpar_io_capable --filter "lpar_ids=3"
3,Running,inactive,10.176.x.x,AIX 5.3 5300-12-05-1140,0,0,0

But I check on my AIX lpar, the rmc is still active
Code:
[abc] / > lssrc -s ctrmc
Subsystem         Group            PID          Status
 ctrmc            rsct             385218       active

I am still finding the way to check on VIOS rmc state.

so, why the HMC cannot detect the rmc state.

What I can do to get HMC see the state of lpar rmc state. Please advise.
 

10 More Discussions You Might Find Interesting

1. AIX

Dlpar

Hi, Anybody had a problem trying to rmdev a scsi device and get the following error : root@:/> rmdev -dlscsi3 -R Method error (/usr/lib/methods/ucfgncr_scsi): 0514-062 Cannot perform the requested function because the specified device is busy. I can't... (1 Reply)
Discussion started by: stumpy
1 Replies

2. AIX

DLPAR Error

Hello, This is the foll error wen i try doin DLPAR from my VIO after adding the virtual adpaters on my clients: HSCL294C DLPAR ADD Virtual I/O resources failed: com.ibm.hsc.common.exceptions.PIHscClientException: HSCL294C DLPAR ADD Virtual I/O... (0 Replies)
Discussion started by: lildudesaif
0 Replies

3. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

4. AIX

HMC - tracking dlpar

I am trying to generate a report to track dlpar operation performed on a MS and was wondering if anyone has done this before. I can get history from HMC using lssvcevents , but this does not give me details as to what quantity was added or removed . Any thoughts ? Thanks (3 Replies)
Discussion started by: mk8570
3 Replies

5. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies

6. AIX

DLPAR capable with IVM - checks to do

I cannot find the post with the comment that DLPAR capability was not working with IVM. The two commands that need to be run are (as root, padmin does not know this command): VIOS: lsrsrc IBM.MngNode CLIENTS: lsrsrc IBM.MCP Examples: # lsrsrc IBM.MngNode Resource Persistent Attributes for... (2 Replies)
Discussion started by: MichaelFelt
2 Replies

7. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

8. AIX

System monitoring with RMC/RSCT

Hi all, is any of you using RMC for monitoring your LPARs? Is it viable? I know the IBM Magazine article and the Redbooks about it but I would like to hear from first hand. Thanks in advance for sharing your experience! (7 Replies)
Discussion started by: zaxxon
7 Replies

9. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

10. AIX

AIX: DLPAR VFC - HMC v9

Hey All, I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS. In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the... (1 Reply)
Discussion started by: aixkidbee
1 Replies
ipfstat(8)						      System Manager's Manual							ipfstat(8)

NAME
ipfstat - reports on packet filter statistics and filter list SYNOPSIS
ipfstat [ -6aAdfghIilnoRsv ] ipfstat -t [ -6C ] [ -D <addrport> ] [ -P <protocol> ] [ -S <addrport> ] [ -T <refresh time> ] DESCRIPTION
ipfstat examines /dev/kmem using the symbols _fr_flags, _frstats, _filterin, and _filterout. To run and work, it needs to be able to read both /dev/kmem and the kernel itself. The kernel name defaults to /boot/kernel/kernel. The default behaviour of ipfstat is to retrieve and display the accumulated statistics which have been accumulated over time as the kernel has put packets through the filter. OPTIONS
-6 Display filter lists and states for IPv6, if available. -a Display the accounting filter list and show bytes counted against each rule. -A Display packet authentication statistics. -C This option is only valid in combination with -t. Display "closed" states as well in the top. Normally, a TCP connection is not displayed when it reaches the CLOSE_WAIT protocol state. With this option enabled, all state entries are displayed. -d Produce debugging output when displaying data. -D <addrport> This option is only valid in combination with -t. Limit the state top display to show only state entries whose destination IP address and port match the addrport argument. The addrport specification is of the form ipaddress[,port]. The ipaddress and port should be either numerical or the string "any" (specifying any IP address resp. any port). If the -D option is not specified, it defaults to "-D any,any". -f Show fragment state information (statistics) and held state information (in the kernel) if any is present. -g Show groups currently configured (both active and inactive). -h Show per-rule the number of times each one scores a "hit". For use in combination with -i. -i Display the filter list used for the input side of the kernel IP processing. -I Swap between retrieving "inactive"/"active" filter list details. For use in combination with -i. -n Show the "rule number" for each rule as it is printed. -o Display the filter list used for the output side of the kernel IP processing. -P <protocol> This option is only valid in combination with -t. Limit the state top display to show only state entries that match a specific pro- tocol. The argument can be a protocol name (as defined in /etc/protocols) or a protocol number. If this option is not specified, state entries for any protocol are specified. -R Don't try to resolve addresses to hostnames and ports to services while printing statistics. -s Show packet/flow state information (statistics only). -sl Show held state information (in the kernel) if any is present (no statistics). -S <addrport> This option is only valid in combination with -t. Limit the state top display to show only state entries whose source IP address and port match the addrport argument. The addrport specification is of the form ipaddress[,port]. The ipaddress and port should be either numerical or the string "any" (specifying any IP address resp. any port). If the -S option is not specified, it defaults to "-S any,any". -t Show the state table in a way similar to the way top(1) shows the process table. States can be sorted using a number of different ways. This option requires curses(3) and needs to be compiled in. It may not be available on all operating systems. See below, for more information on the keys that can be used while ipfstat is in top mode. -T <refreshtime> This option is only valid in combination with -t. Specifies how often the state top display should be updated. The refresh time is the number of seconds between an update. Any positive integer can be used. The default (and minimal update time) is 1. -v Turn verbose mode on. Displays more debugging information. When used with either -i or -o, counters associated with the rule, such as the number of times it has been matched and the number of bytes from such packets is displayed. For "keep state" rules, a count of the number of state sessions active against the rule is also displayed. SYNOPSIS
The role of ipfstat is to display current kernel statistics gathered as a result of applying the filters in place (if any) to packets going in and out of the kernel. This is the default operation when no command line parameters are present. When supplied with either -i or -o, it will retrieve and display the appropriate list of filter rules currently installed and in use by the kernel. One of the statistics that ipfstat shows is ticks. This number indicates how long the filter has been enabled. The number is incremented every half-second. STATE TOP
Using the -t option ipfstat will enter the state top mode. In this mode the state table is displayed similar to the way top displays the process table. The -C, -D, -P, -S and -T command line options can be used to restrict the state entries that will be shown and to specify the frequency of display updates. In state top mode, the following keys can be used to influence the displayed information: b show packets/bytes from backward direction. f show packets/bytes from forward direction. (default) l redraw the screen. q quit the program. s switch between different sorting criterion. r reverse the sorting criterion. States can be sorted by protocol number, by number of IP packets, by number of bytes and by time-to-live of the state entry. The default is to sort by the number of bytes. States are sorted in descending order, but you can use the r key to sort them in ascending order. STATE TOP LIMITATIONS
It is currently not possible to interactively change the source, destination and protocol filters or the refresh frequency. This must be done from the command line. The screen must have at least 80 columns. This is however not checked. When running state top in IPv6 mode, the screen must be much wider to display the very long IPv6 addresses. Only the first X-5 entries that match the sort and filter criteria are displayed (where X is the number of rows on the display. The only way to see more entries is to resize the screen. FILES
/dev/kmem /dev/ipl /dev/ipstate /kernel SEE ALSO
ipf(8) BUGS
none known. ipfstat(8)
All times are GMT -4. The time now is 10:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy