The presence of PEM modules in the chassis affects the logical network interface name to which the NEM ports map when Linux is installed. The user is currently required to explicitly specify different logical interface names, depending on the number of PEM modules installed on the blade. In particular, the user must specify both bootnetworkdevice and networkdevice options as specified in the below tables. The following tables shows the valid values for 2-port PCI express modules:
Table 2–1 One 2-port PEM
Interface |
bootnetworkdevice |
networkdevice |
---|---|---|
NEM0 |
eth0 |
eth2 |
NEM1 |
eth1 |
eth3 |
Table 2–2 Two 2-port PEMs
Interface |
bootnetworkdevice |
networkdevice |
---|---|---|
NEM0 |
eth0 |
eth4 |
NEM1 |
eth1 |
eth5 |
Since the PEM configuration may vary, the general formula is given below in the following table:
Interface |
bootnetworkdevice |
networkdevice |
---|---|---|
NEM0 |
eth0 |
ethX where X = 0 + number of ports on 1st PEM + number of ports on 2nd PEM |
NEM1 |
eth1 |
ethX where X = 1 + number of ports on 1st PEM + number of ports on 2nd PEM |
You cannot configure different bootip and ip settings as part of the load command. When OS deployment completes, only one interface will be configured.
Linux deployment on a Sun Blade X6220 server goes into interactive mode if you do not specify the correct networkdevice option when PEMs are present.