Yep, I have all of that (or I think so at this time<G>).

I wanted to see who was connected to the vswitch.  I know that vswitch
is just a special type of guest lan, so I should have known to look at
the guest lan type commands.

Tom Duerbusch
THD Consulting
I "should" go get a beer, now.

>>> [EMAIL PROTECTED] 10/21/05 2:33 PM >>>
Tom: You need a minimum  of one VM TCPIP controller machine. The 
controller machine manages the vswitch for availability. The real 
devices are attached to the controller at vswitch creation or recovery

to an available controller. The controller does not have DEVICE/LINK 
statements, it does not run it as IP adapter. If you want a VM TCPIP 
stack to use the vswitch as an IP adaptor you need to give it a NICDEF

and couple it over to the vswitch guest lan (sorry Alan for calling it
a 
vswitch guest lan).
So you would then have two VM TCPIP stacks, one as a controller, and
the 
other as a user of the vswitch.

Bytes in/out come from a NETSTAT DEVLINK pointing at the name of tcpip

controller:
netstat devlink tcp tcpiplz                                          
VM TCP/IP Netstat Level 510                                          
                                                                     
Device VSWITCHDEV              Type: VSWITCH-IUCV   Status: Connected
  Queue size: 0     CPU: 0     IUCVid: *VSWITCH     Priority: B      
    Link VSWITCHLINK           Type: IUCV           Net number: 1    
      BytesIn: 790             BytesOut: 924                         


or from asking the tcpip stack using an adapter on the guest lan:
netstat devlink tcp tcpiply                                            
  
VM TCP/IP Netstat Level 510                                            
  
                                                                       
  
Device [EMAIL PROTECTED]                Type: OSD            Status: Ready      
  
  Queue size: 0     CPU: 0     Address: 0800        Port name:
UNASSIGNED 
  IPv4 Router Type: NonRouter  Arp Query Support: Yes                  
  
    Link OSASERV               Type: QDIOETHERNET   Net number: 0      
  
      BytesIn: 427469          BytesOut: 0                             
  
      Forwarding: Enabled      MTU: 1500            IPv6: Disabled     
  
      Broadcast Capability: Yes                                        
  
      Multicast Capability: Yes                                        
  
      Group                                   Members                  
  
      -----                                   -------                  
  
      224.0.0.1                                  1                     
  



David

Tom Duerbusch wrote:

>I have vswitch running over on the IFL lpar.  Still only testing.
>
>Great...neat...
>
>I connected to it via VM's TCP/IP stack.
>I've connected to it via 64 bit SLES9.
>
>Seems to all work.
>
>But now that traffic isn't being routed via the VM TCP/IP stack, the
>information that I was getting from NETSTAT, just isn't there
anymore.
>
>I use to be able to see what was connected to me.
>I use to be able to see the byte count of data that was sent (netstat
>dev).
>
>Just kind of wondering how I can tell when it is being used and what
>kind of and amount of activity that is on it.
>
>Thanks
>
>Tom Duerbusch
>THD Consulting
>
>
>
>  
>

Reply via email to