I know the answer.   Promiscuous mode is a two step process.  First the
user has to be authorized to use promiscuous mode.  This can be done
through CP or RACF.  Since you are using RACF, you will need to check the
RACF books to see how to grant authority for promisuous mode.  The second
step is to place your nic into promiscuous mode. You get a positive reply
because the second step completes successfully.  If you were to uncouple
your nic from this LAN and couple to one where you are authorized for
promiscuous mode, your nic would already be enabled for promisuous mode.
In short, your nic is ready but your administer doesn't want you to be
able to sniff the traffic (just another security measure).  Let me know if
I can be of more help.

Tracy (Bolinda) Adams
[EMAIL PROTECTED]
z/VM Development - Virtual Networking




Ronald van der Laan <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[email protected]>
07/08/2006 06:48 AM
Please respond to
Linux on 390 Port <[email protected]>


To
[email protected]
cc

Subject
A question about using a NIC in promiscuous mode






Hi,

I'm running z/VM 5.2 and RACF/VM with APAR VM63750 installed.
My Linux guest has CONTROL access to the vswitch resource.
When I try to set the NIC into promiscous mode, I get a positive reply,
but
checking the NIC says something differently.

lnxnew03:/ # hcp set nic d002
promisc
hcp set nic d002 promisc
Promiscuous Mode has been enabled for device D002
lnxnew03:/ # hcp q nic d000 details
hcp q nic d000 details
Adapter D000  Type: QDIO      Name: LNXNEW03    Devices: 3
  Port 0 MAC: 02-E0-12-06-82-03  VSWITCH: SYSTEM L2HA
      RX Packets: 20         Discarded: 0          Errors: 0
      TX Packets: 38         Discarded: 0          Errors: 0
      RX Bytes: 2830                 TX Bytes: 2859
  Connection Name: HALLOLE   State: Session Established
      Device: D000  Unit: 000   Role: CTL-READ
      Device: D001  Unit: 001   Role: CTL-WRITE
      Device: D002  Unit: 002   Role: DATA
      Options: Broadcast Multicast IPv6 IPv4 VLAN Promiscuous_Denied
        Unicast IP Addresses:
          9.149.68.203         MAC: 02-E0-12-06-82-03
          FE80::2E0:1200:106:8203 MAC: 02-E0-12-06-82-03 Local
        Multicast IP Addresses:
          224.0.0.1            MAC: 01-00-5E-00-00-01
          FF02::1              MAC: 33-33-00-00-00-01
          FF02::1:FF06:8203    MAC: 33-33-FF-06-82-03 Local

And from the RAC RL VMLAN SYSTEM.L2HA:
CLASS      NAME
-----      ----
VMLAN      SYSTEM.L2HA

USER      ACCESS   ACCESS COUNT
----      ------   ------ -----
LNXNEW03  CONTROL     000000


Q VMLAN
VMLAN maintenance level:
  Latest Service: VM63784
VMLAN MAC address assignment:
  MACADDR Prefix: 02E012
  MACIDRANGE SYSTEM: 000001-FFFFFF
             USER:   000000-000000
VMLAN default accounting status:
  SYSTEM Accounting: OFF       USER Accounting: OFF
VMLAN general activity:
  PERSISTENT Limit: INFINITE   Current: 1
  TRANSIENT  Limit: INFINITE   Current: 0

Q VSWITCH
VSWITCH SYSTEM L2HA     Type: VSWITCH Connected: 35   Maxconn: INFINITE
  PERSISTENT  RESTRICTED    NONROUTER                 Accounting: OFF
  VLAN Unaware
  State: Ready
  IPTimeout: 5         QueueStorage: 8
  Portname: UNASSIGNED RDEV: 0030 Controller: VSWCTL2  VDEV:  0030
  Portname: UNASSIGNED RDEV: 0040 Controller: NONE


I'm running on a z990 processor and want to check the traffic on the
vswitch.
Does someone know what I'm doing wrong?

Ronald van der Laan

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to