network naming eth0 as em1 , p1p1

I have observed some different naming for ethernet interfaces in the Server.

You can find  the reason here

http://serverfault.com/questions/441367/fedora-17-ifconfig-eth0-returns-an-error-message-why-did-linux-change-eth0-to-e

====================================================================

It's consistent network device naming.

Systems, particularly servers, with multiple network ports, name the ports ethX in a non-deterministic order, and are therefore not useful for system administrators.

System Administrators can then use BIOS-provided names, which are consistent and not arbitrarily named, for their network ports. This eliminates the confusion that non-deterministic naming brings, and eliminates the use of hard-coded MAC address based port renaming which a) is racy and error-prone, and b) introduces state into an otherwise stateless system.

This change affects most desktop, notebook, and server-class systems.

The em means that the interface is embedded onto the motherboard. Other names apply for add-on cards:p#p# names refer to PCI (and its modern derivatives) expansion cards, where the first number is the slot on the motherboard which they're plugged into, the second number is the port on the card (a card may contain multiple ports) and the third number, if present, is a virtual function number.

====================================================================