| Networking information produced by commands is also peculiar to the vPar on which you've issued the command. Networking configuration of vPars is covered in Chapter 13. Let's take a look at the network interface on two different vPars configured on the same server. First let's look at the output of vPar cable1 with a hostname of cvhdcon3: # hostname cvhdcon3 # netstat -I lan0 Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan0 1500 172.16.15.0 cvhdcon3 12785 0 11855 0 3 # # netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan0 1500 172.16.15.0 172.16.15.36 12990 0 12052 0 3 lo0 4136 127.0.0.0 127.0.0.1 7616 0 7616 0 0 # # lanscan Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Path Address In# State NamePPA ID Type Support Mjr# 0/0/0/0 0x00306E06F6BA 0 UP lan0 snap0 1 ETHER Yes 119 # This output shows that lan0 is the network interface devoted to vPar cable1 on this server. The lanscan output shows that this interface has a hardware path of 0/0/0/0. This is on the Core I/O card that was configured as a component of the vPar when it was created with -a io:0/0. The LAN interface on the Core I/O card was not explicitly called out when cable1 was created because 0/0/0/0 is an implied component of the Core I/O card at 0/0. Let's now take a look at the second vPar running on this server, called cable2 with a hostname of cvhdcon4: # hostname cvhdcon4 # netstat -I lan1 Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan1 1500 172.16.14.0 cvhdcon4 3463 0 1603 0 2 # # netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan1 1500 172.16.14.0 172.16.14.44 3819 0 1948 0 2 lo0 4136 127.0.0.0 127.0.0.1 916 0 916 0 0 # # lanscan Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Path Address In# State NamePPA ID Type Support Mjr# 0/10/0/0 0x00306E0653E8 1 UP lan1 snap1 1 ETHER Yes 119 # This output shows that lan1 is the network interface devoted to vPar cable2 on this server. The lanscan output shows that this interface has a hardware path of 0/10/0/0. The LBA of 0/10 was configured as a component of the vPar when it was created with -a io:0/10/. Unlike the LAN interface on the Core I/O card that was an implied component, this LAN interface is in a separate PCI slot and LBA and therefore had to be specified explicitly when the vPar was created. Running lanadmin on cable1 produces more detailed output related to lan0, as shown in the following listing: # lanadmin LOCAL AREA NETWORK ONLINE ADMINISTRATION, Version 1.0 Mon, Oct 15,2001 14:41:23 Copyright 1994 Hewlett Packard Company. All rights are reserved. Test Selection mode. lan = LAN Interface Administration menu = Display this menu quit = Terminate the Administration terse = Do not display command menu verbose = Display command menu Enter command: lan LAN Interface test mode. LAN Interface PPA Number = 0 clear = Clear statistics registers display = Display LAN Interface status and statistics registers end = End LAN Interface Administration, return to Test Selection menu = Display this menu ppa = PPA Number of the LAN Interface quit = Terminate the Administration, return to shell reset = Reset LAN Interface to execute its selftest specific = Go to Driver specific menu Enter command: d LAN INTERFACE STATUS DISPLAY Mon, Oct 15,2001 14:42:33 PPA Number = 0 Description = lan0 HP PCI 10/100Base-TX Core [100BASE-TX,HD,AUTO,TT=1500 Type (value) = ethernet-csmacd(6) MTU Size = 1500 Speed = 100000000 Station Address = 0x306e06f6ba Administration Status (value) = up(1) Operation Status (value) = up(1) Last Change = 755 Inbound Octets = 2101014 Inbound Unicast Packets = 9830 Inbound Non-Unicast Packets = 1692 Inbound Discards = 0 Inbound Errors = 0 Inbound Unknown Protocols = 772 Outbound Octets = 1184028 Outbound Unicast Packets = 9613 Outbound Non-Unicast Packets = 8 Outbound Discards = 0 Outbound Errors = 0 Outbound Queue Length = 0 Specific = 655367 Press <Return> to continue This lanadmin output shows lan0 as the configured LAN interface on cable1. Let's now run lanadmin on cable2 and see for what LAN interface it produces an output: # lanadmin LOCAL AREA NETWORK ONLINE ADMINISTRATION, Version 1.0 Mon, Oct 15,2001 14:41:23 Copyright 1994 Hewlett Packard Company. All rights are reserved. Test Selection mode. lan = LAN Interface Administration menu = Display this menu quit = Terminate the Administration terse = Do not display command menu verbose = Display command menu Enter command: lan LAN Interface test mode. LAN Interface PPA Number = 1 clear = Clear statistics registers display = Display LAN Interface status and statistics registers end = End LAN Interface Administration, return to Test Selection menu = Display this menu ppa = PPA Number of the LAN Interface quit = Terminate the Administration, return to shell reset = Reset LAN Interface to execute its selftest specific = Go to Driver specific menu Enter command: d LAN INTERFACE STATUS DISPLAY Mon, Oct 15,2001 14:40:48 PPA Number = 1 Description = lan1 HP A5230A/B5509BA PCI 10/100Base-TX Addon 100BASE-TX Type (value) = ethernet-csmacd(6) MTU Size = 1500 Speed = 100000000 Station Address = 0x306e0653e8 Administration Status (value) = up(1) Operation Status (value) = up(1) Last Change = 726 Inbound Octets = 4329654 Inbound Unicast Packets = 3157 Inbound Non-Unicast Packets = 23708 Inbound Discards = 0 Inbound Errors = 0 Inbound Unknown Protocols = 20720 Outbound Octets = 401517 Outbound Unicast Packets = 3189 Outbound Non-Unicast Packets = 7 Outbound Discards = 0 Outbound Errors = 0 Outbound Queue Length = 0 Specific = 655367 Press <Return> to continue This lanadmin output shows lan1 as the configured LAN interface on cable2. Producing information specific to the vPar in which you issue a command is what you can expect when working at the command line with vPars. Next, let's take a look at a couple of GlancePlus/UX outputs. | 
