Cisco Cisco Packet Data Gateway (PDG)
VPC-DI Changes in Release 17
VPC-DI Feature Changes for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
649
BOND0_PRIMARY=ETH0
BOND0_REVERSION_POLICY=0
BOND0_LINK_DETECT=0
BOND0_MII_POLL=100
BOND1_MAP=ETH1,ETH2
BOND1_PRIMARY=ETH1
BOND1_REVERSION_POLICY=0
BOND1_LINK_DETECT=0
BOND1_MII_POLL=100
CSCuq97178 - Should be able to boot SF locally even with passthrough NICs
Applicable Products: VPC-DI
Feature Changes
Passthrough Booting Locally
For a CF, if the network interface is configured and a slot number is available, the CF will try to boot from the other CF
first. It tries boots based on its boot.sys if the CF fails to boot from the other CF (current behavior).
first. It tries boots based on its boot.sys if the CF fails to boot from the other CF (current behavior).
If the network interface is not configured or a slot number is not available, the CF will boot based on its boot.sys
without trying to boot from the other CF. This is the scenario for passthrough NIC.
without trying to boot from the other CF. This is the scenario for passthrough NIC.
For an SF, if the network interface is configured and a slot number is available, the SF will boot from either of the CFs
(current behavior)
(current behavior)
If the network interface is not configured or a slot number is unavailable, the SF will boot from its local partition 1 to
load “/boot1/staros.bin”. This is the scenario for passthrough NIC.
load “/boot1/staros.bin”. This is the scenario for passthrough NIC.
CSCur44411 - DI: rc should reboot if masterslot can't be determined
Applicable Products: VPC-DI
Feature Changes
SF Reboot Timeout When CF Cannot Be Detected
An SF will reboot itself after a 3-minute timeout period if it cannot detect a CF in the master slot.