Forum Discussion

shahfar's avatar
shahfar
Level 5
14 years ago

Fails to detect network interface after successful BMR restore

Hi Everyone,

I sucessfully completed a Solaris (SPARC) 9 restore (Solaris 10 boot server with Solaris 9 SRT) through BMR. The problem is, after the restore process drops me to the OK prompt after completion and I start the boot from disk, the network interface fails to come up (see bold lines below):

*******************************

SunOS Release 5.9 Version Generic_122300-56 64-bit

Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.

Use is subject to license terms.

WARNING: forceload of misc/md_trans failed

WARNING: forceload of misc/md_raid failed

WARNING: forceload of misc/md_hotspares failed

WARNING: forceload of misc/md_sp failed

ifconfig: plumb: ce0: no such interface

moving addresses from failed IPv4 interfaces: ce0 (couldn't move, no alternative interface).

Hostname: sec25-8

Configuring /dev and /devices

/kernel/drv/sparcv9/fcsm: undefined symbol 'fc_ulp_get_port_login_params'

WARNING: mod_load: cannot load module 'fcsm'

Configuring the /dev directory (compatibility devices)

The system is coming up.  Please wait.

Started Symantec Private Branch Exchange

starting rpc services: rpcbind done.

Setting default IPv4 interface for multicast: add net 224.0/4: gateway sec25-8

syslog service starting.

NetBackup Authentication daemon not started.

NetBackup network daemon started.

NetBackup client daemon started.

NetBackup SAN Client Fibre Transport daemon started.

NetBackup Bare Metal Restore Boot Server daemon started.

metaset: sec25-8: metad client create: RPC: Rpcbind failure

 

V-128-749 Operation failed due to network problem.

[Error] V-122-3 Operation failed.

S99sneep: Chassis Serial not available from system eeprom

S99sneep: Chassis Serial not available from system eeprom

volume management starting.

*******************************

System sucessfully comes up after this. I tried to manually bring up the interface after system starts (accessing through serial console) but the system does not detect the NIC. Upon reboot (without doing any config changes), the system restores the original NIC config:

************************************

SunOS Release 5.9 Version Generic_122300-56 64-bit

Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.

Use is subject to license terms.

WARNING: forceload of misc/md_trans failed

WARNING: forceload of misc/md_raid failed

WARNING: forceload of misc/md_hotspares failed

WARNING: forceload of misc/md_sp failed

configuring IPv4 interfaces: ce0.

Hostname: sec25-8

The system is coming up.  Please wait.

Started Symantec Private Branch Exchange

starting rpc services: rpcbind done.

Setting netmask of ce0 to 255.255.254.0

Setting default IPv4 interface for multicast: add net 224.0/4: gateway sec25-8

syslog service starting.

NetBackup Authentication daemon not started.

NetBackup network daemon started.

NetBackup client daemon started.

NetBackup SAN Client Fibre Transport daemon started.

NetBackup Bare Metal Restore Boot Server daemon started.

S99sneep: Chassis Serial not available from system eeprom

S99sneep: Chassis Serial not available from system eeprom

volume management starting.

************************************

7.1.x and Earlier
Backup and Recovery
NetBackup
Recovering

5 Replies

Sort By
  • mandar_khanolka's avatar
    mandar_khanolka
    Level 6
    14 years ago

    Looks like during first boot the system failed to detect NIC device while probing for existing devices. Hence the device file not generated for NIC and later it failed to set IP.

    This has never been observed during our tests and BMR does not set any IP or probes for devices after restore. Its UNIX OS who probes for devices during boot and creates /dev files for them.

    Probably "one more" reboot is the only good solution here. :-)

    Thanks.

    -Mandar

  • shahfar's avatar
    shahfar
    Level 5
    14 years ago

    Hi Mandar,

    Thank you for your response. In any case, we have verified multiple times that the recovered Solaris box does a reconfigure boot after a sucessful restore which basically re-builds /dev and /devices. Subsequent reboots do not show the devices being re-configured. Somehow, somewhere BMR tells the machines to do a 'boot -r' of some sort. Would you be able to confirm this please? Thank you!

    WBR

  • mandar_khanolka's avatar
    mandar_khanolka
    Level 6
    14 years ago

    BMR does not do anything like "boot -r" explicitly, it solaris system itself identifies system has been re-configured during BMR recovery process and hence does re-probes devices.

    Thanks.

    -Mandar

  • shahfar's avatar
    shahfar
    Level 5
    14 years ago

    Hi Mandar,

    Thank you for your response. In essence, this device reconfiguration is not allowing the NIC to be detected. As per my understanding, the system only does a reconfiguration reboot when you issue a boot -r command or create a file called 'reconfigure' on the system. But is there any explicit way we can disable this?

    Since the reconfiguration is taking place, the finalization process gets stuck on the NBU console. Is this a noted issue? Is there an internal technote for it?

    Thank you.

     

    WBR

  • mandar_khanolka's avatar
    mandar_khanolka
    Level 6
    14 years ago

    Hi WBR

    >> But is there any explicit way we can disable this?

    At glance I am not sure if this can be done.

    As I said ealier, we have not observed this case and any re-configuration delay in our env before.

    No technote has been published on this case.

    Thanks.

    -Mandar