At the time of publishing those last WBs we did not have a Subscriber - and
perhaps the wording wasn't the best.
Now (and for sometime now) we do have both Pub (10.x.200.21) and a Sub
(10.x.200.20) live in every pod.
Hope that clears some things up :)
Mark Snow
CCIE #14073 (Voice, Security)
CCSI #31583
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.309.413.4097
Mailto: [EMAIL PROTECTED]
IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On Demand
and Audio Certification Training Tools for the Cisco CCIE R&S Lab, CCIE
Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and CCIE Storage
Lab Certifications.
On Feb 23, 2008, at 2:27 PM, Mark Cardwell wrote:
Question and concern. On the ebooks and printed WB, It states that there is
no publisher (.20) and just to assume a publisher. So given how can we fix
replication on a server that does not exist. I am very confused and am
wonder what you are referring to when you state this is an inherent
troubleshooting task. And another thing I am confused on is if there is a
Pub and a Sub then why am I logging into the Sub (according to the WB
documentation).
Cheers!
Mark Cardwell | System Engineer | Presidio Networked Solutions |
[EMAIL PROTECTED]| Cell: 571.225.0132 | Office: 301.623.2000| FAX:
301.313.2400
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Snow
Sent: Friday, February 22, 2008 1:19 PM
To: Moore, Neil
Cc: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] SQL replication check\fix Q.
SA user (even though mentioned in that article) is not ever to be used.
Use local authentication instead - will work every time - even between
boxes.
And yes - SQL replication is broken on all of our Subscribers in every pod -
and that is no accident! :)
It is there as an "inherent troubleshooting" task - which is a testable
'topic' in the lab - so beware - things may not always be as they seem on
the surface!
HTH,
Mark Snow
CCIE #14073 (Voice, Security)
CCSI #31583
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.309.413.4097
Mailto: [EMAIL PROTECTED]
IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On Demand
and Audio Certification Training Tools for the Cisco CCIE R&S Lab, CCIE
Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and CCIE Storage
Lab Certifications.
On Feb 22, 2008, at 12:38 PM, Moore, Neil wrote:
Hi there folks!
I'm after any thoughts\tips on checking the sql replication's all good
before you start you lab configs (virtual and real).
My last couple of vrack sessions I've had lots of probs with this. The
replication is never setup and running at the start of the vrack sessions so
I update lmhosts (checked the cache is good), check connectivity etc, and
then tried the following procedure:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801d11a6.shtml
for the sa account pwrd I'm trying cisco and blank, I've reset these on both
boxes aswell, same. Seems to me like some sort of authentication issue.
I've even put dblhelper on the box & that can't sort it & this always works
a treat in the field!!
So I guess my questions are:
What check do you folks do to check the replication (add a dev & check the
device table?)
What procedure do you follow to get the replication up and running at the
start of your vrack sessions (proctorlabs.com)?
Is this a 'task' for all proctorlab vrack sessions only? (is this just a
vmare 'feature'?)
In the real lab would we be expected to do this kind of sql troubleshooting,
reseting sa pwrds, assigning roles etc in SQL?
What am I missing!!?
Any help'd be appreciated.
Cheers,
Neil (UK)
consulting | technology | outsourcing
BT Lynx is a Cisco Systems Gold Certified Partner, Microsoft Gold Certified
Partner and HP Business Partner Select / Authorised Services Delivery
Partner.
Sales Offices: Sheffield, London City
DISCLAIMER:
This message is intended only for the use of the person(s) ('Intended
Recipient') to whom it is addressed. It may contain information, which is
privileged and confidential. Accordingly any dissemination, distribution,
copying or other use of this message or any of its content by any person
other than the Intended Recipient may constitute a breach of civil or
criminal law and is strictly prohibited. If you are not the Intended
Recipient, please contact the sender as soon as possible. Neither BT Lynx or
the sender accept any responsibility for viruses and it is your
responsibility to scan the email and attachments. Any liability arising from
any third party acting on any information contained in this email is hereby
excluded. BT Lynx will hold data provided by you for marketing and
promotional purposes unless otherwise advised.
Please see our Statement of Privacy at http://www.btlynx.com/privacy.asp
BT Lynx Ltd Registered No.2277581 - Registered Office: 3 Midland Way,
Barlborough, Chesterfield, S43 4XA - A BT Group plc company
<Mark Cardwell.vcf>
