| The LAN cards on your system are also easy to identify with ioscan. To see only the listing of LAN cards on a system, we would issue the following command: # ioscan -f | grep lan lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE PCI Ethernet (10110019) lan 1 0/4/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon lan 3 0/5/0/0/4/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 port lan 4 0/5/0/0/5/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 port lan 5 0/5/0/0/6/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 port lan 6 0/5/0/0/7/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 port lan 2 1/12/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon # This system has seven LAN interfaces. It has the built-in LAN interface, two add-on LAN cards, and a four-port card. Although this system was not used in our earlier example, I wanted to show a listing of a system with a variety of LAN interfaces present. Going back to our earlier example, our system has three LAN interfaces as shown in the following ioscan listing: cvhdcon3:/ # ioscan -f | grep lan lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Ba se-TX Core lan 1 0/10/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509 BA PCI 10/100Base-TX Addon lan 2 0/12/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509 BA PCI 10/100Base-TX Addon cvhdcon3:/ # | | The LAN card at 0/0 has been asssigned to cable1, and the card at 0/10 has been assigned to cable2, as shown in the following vparstatus -v listing: |
# vparstatus -v [Virtual Partition Details] Name: cable1 State: Up Attributes: Dynamic,Manual Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/3 Bound by User [Path]: Bound by Monitor [Path]: 33 Unbound [Path]: [IO Details] 0.0 <-- cable1 LAN on 0/0 but not shown 0.0.1.1.2.0 BOOT [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 1024 [Virtual Partition Details] Name: cable2 State: Up Attributes: Dynamic,Manual Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/3 Bound by User [Path]: Bound by Monitor [Path]: 37 Unbound [Path]: [IO Details] 0.8.0.0.8.0.5.0.0.0, BOOT 0.10 <-- cable2 LAN [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 1024 # | | The LAN interface on the Core I/O card at 0/0/0/0 is not called out explicitly in the vparstatus output. The console at 0/0/4/0 is also an implied component of this vPar. Both of these components are part of the Core I/O card that we specified as part of cable1 with the -a io:0/0 argument to the vparcreate command. |
| | The unassigned LAN interface can be added to cable1 or cable2 with the vparmodify command. At the time of this writing, however; I/O components can't be added dynamically, and the vPar would have to be down in order to add LAN or any other I/O component. You can, however; use Online Replacement and Addition (OLAR) of components in vPars. If you |
had, for instance, assigned an I/O path to a vPar and then you physically add a component to that I/O slot then it is part of the vPar. |