Fw-01# hw-module module 1 reset The module in slot 1 should be shut down before resetting it or loss of configuration may occur. Reset module in slot 1? confirm Reset issued for module in slot 1 Now you need to wait for a while (about 2 minut es during Initialization state): fw-01# show module 1 details. Symptom: SIP remains in disabled state even if 'no hw-module slot X shutdown' command is entered in order to undo the previosly configured 'hw-module slot X shutdown' (config)#no hw-module slot X shutdown #show platform Slot Type State Insert time (ago) - - - - X ASR1000-SIP10 disabled 2d03h Conditions: 'hw-module slot X shutdown' was configured multiple times on the same slot. Hw-module slot num reset power-cycle but if a sup card and in rommon (message 'Module not completely up') it does not want to play. (assuming its not my equipment). Off to site we go. C6816-X-LE#sh hw-module slot 1 oversubscription port-group oversubscription-mode 1 enabled 2 disabled The Catalyst 6840-X series chassis provides extremely high levels of scalability and performance, with the size and economics of an innovative fixed architecture.

1. Hw-module Slot X Oversubscription
2. Hw-module Slot Reset
3. Hw-module Location 0/0/cpu0 Port-mode
4. Hw-module Subslot
5. Hw-module Slot R1 Stop
6. Hw-module Session
7. Hw-module Slot Shutdown

Can anyone comment on RSP redundancy with SSO mode?
I have a test 7507 with rsp-k4pv-mz.120-32.S8.bin on both RSP2s. I've done
this:
service single-slot-reload-enable
redundancy
no keepalive-enable
mode sso
And it doesn't seem to ever sync the slave
ranttest#show red
Redundant System Information :
------------------------------
Available system uptime = 14 minutes, 49 seconds
Switchovers system experienced = 0
Standby failures = 0
Last switchover reason = none
Hardware Mode = Duplex
Configured Redundancy Mode = sso
Operating Redundancy Mode = hsa
Maintenance Mode = Disabled
Communications = Down Reason: Simplex mode
Current Processor Information :
-------------------------------
Active Location = slot 2
Current Software state = ACTIVE
Uptime in current state = 13 minutes, 24 seconds
Image Version = Cisco Internetwork Operating System

Hw-module Slot X Oversubscription

Software
IOS (tm) RSP Software (RSP-K4PV-M), Version 12.0(32)S8, RELEASE SOFTWARE
(fc1)

Hw-module Slot Reset

Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by cisco Systems, Inc.
Compiled Mon 20-Aug-07 16:34 by leccese
BOOT =
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Peer (slot: 3) information is not available because it is in 'DISABLED'
state
ranttest#redundancy force-switchover
Cannot perform switchover until the standby is fully initialized.
The box is up, its got two OSPF adjacencies, maybe a hundred routes - its
not doing anything fancy, so I'm kind of stuck here. The production target
is 7507s /w RSP4s, the same OSPF, and about 180k routes via BGP. Any idea

Hw-module Location 0/0/cpu0 Port-mode

what might be wrong here?
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net

Hw-module Subslot

https://puck.nether.net/mailman/listinfo/cisco-nsp

Hw-module Slot R1 Stop

archive at http://puck.nether.net/pipermail/cisco-nsp/

#include < boot_control.h >

Data Fields
struct hw_module_t	common
void(*	init )(struct boot_control_module *module)
unsigned(*	getNumberSlots )(struct boot_control_module *module)
unsigned(*	getCurrentSlot )(struct boot_control_module *module)
int(*	markBootSuccessful )(struct boot_control_module *module)
int(*	setActiveBootSlot )(struct boot_control_module *module, unsigned slot)
int(*	setSlotAsUnbootable )(struct boot_control_module *module, unsigned slot)
int(*	isSlotBootable )(struct boot_control_module *module, unsigned slot)
const char *(*	getSuffix )(struct boot_control_module *module, unsigned slot)
int(*	isSlotMarkedSuccessful )(struct boot_control_module *module, unsigned slot)
void *	reserved [31]

Detailed Description

Every hardware module must have a data structure named HAL_MODULE_INFO_SYM and the fields of this data structure must begin with hw_module_t followed by module specific information.

Definition at line 50 of file boot_control.h .

Field Documentation

Hw-module Session

Definition at line 51 of file boot_control.h .

unsigned(* getCurrentSlot)(struct boot_control_module *module)

Definition at line 76 of file boot_control.h .

unsigned(* getNumberSlots)(struct boot_control_module *module)

Definition at line 64 of file boot_control.h .

const char*(* getSuffix)(struct boot_control_module *module, unsigned slot)

Definition at line 118 of file boot_control.h .

void(* init)(struct boot_control_module *module)

Definition at line 57 of file boot_control.h .

int(* isSlotBootable)(struct boot_control_module *module, unsigned slot)

Definition at line 110 of file boot_control.h .

int(* isSlotMarkedSuccessful)(struct boot_control_module *module, unsigned slot)

Hw-module Slot Shutdown

Definition at line 126 of file boot_control.h .

int(* markBootSuccessful)(struct boot_control_module *module)

Definition at line 84 of file boot_control.h .

Definition at line 128 of file boot_control.h .

int(* setActiveBootSlot)(struct boot_control_module *module, unsigned slot)

Definition at line 93 of file boot_control.h .

int(* setSlotAsUnbootable)(struct boot_control_module *module, unsigned slot)

Definition at line 101 of file boot_control.h .

The documentation for this struct was generated from the following file:

• hardware/libhardware/include/hardware/ boot_control.h