Sometimes IPMI 2 implementations randomly complain about our math being wrong once in a few thousand tries, start over from scratch should this occur
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@13593 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
parent
89a683b796
commit
55c3a0ef04
@ -652,7 +652,7 @@ sub got_rakp4 {
|
||||
}
|
||||
$byte = shift @data;
|
||||
unless ($byte == 0x00) {
|
||||
if ($byte == 0x02 and $self->{logontries}) { # 0x02 is 'invalid session id', seems that some ipmi implementations sometimes expire a temporary id before I can respond, start over in such a case
|
||||
if (($byte == 0x02 or $byte == 15) and $self->{logontries}) { # 0x02 is 'invalid session id', seems that some ipmi implementations sometimes expire a temporary id before I can respond, start over in such a case
|
||||
$self->relog();
|
||||
return;
|
||||
}
|
||||
@ -692,7 +692,7 @@ sub got_rakp2 {
|
||||
}
|
||||
$byte = shift @data;
|
||||
unless ($byte == 0x00) {
|
||||
if ($byte == 0x02 and $self->{logontries}) { # 0x02 is 'invalid session id', seems that some ipmi implementations sometimes expire a temporary id before I can respond, start over in such a case
|
||||
if (($byte == 0x02 or $byte == 15) and $self->{logontries}) { # 0x02 is 'invalid session id', seems that some ipmi implementations sometimes expire a temporary id before I can respond, start over in such a case
|
||||
$self->relog();
|
||||
return;
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user