by using the link
http://10.1.1.1/ProcessManager/
rather than the link ... http://10.1.1.1/ProcessManager/ ...
signature from switch 10.1.1.1
Dec/31/2008 01:57:41 [ radproxy.c][ 2683]: Invalid signature from switch 10.1.1.1
Dec/31/2008 01:57:46 [ radproxy.c][ 2683]: Invalid signature from switch 10.1.1.1 ... baitakphone via switch 10.1.1.1
What dose Invalid Signature means ? and why SNAC is usign MD5 ...
initially using the command...
nbdevconfig -creatests -st 9 -stype DataDomain -storage_server 10.1.1.1 ... the to use DNS name for the storage servers instead of the IP address (10.1.1.1)..Then i deleted(both storage ... with the command.
nbemmcmd -deletehost -machinename 10.1.1.1 -machinetype ndmp
And then recreated them ...
This issue has been solved
Symantec Corporation 10111 Richmond Avenue, Suite 200
Tue, 14 August, 2012 - 10:00 - 13:00 CDT
SEP 12.1 (Joshua Etsten, Symantec)
Differences of SEP 11 vs 12.1
Overview of Client and Mgmt Console
Insight ...
Symantec Houston -- NEW office
Thu, 19 July, 2012 - 12:00 - 16:00 CDT
Please join us for our next user group meeting on July 19!
Location:
NEW Symantec Office in Houston:
10111 ...
Symantec
10111 Richmond Avenue
Suite 200
Houston, TX 77042
(Security, 12.x, Critical ...
gorup name with ip service group name 1- IP 10.1.1.1 service group name 2- IP 10.1.1.2 service gorup ... are defined and following are service gorup name with ip
service group name 1- IP 10.1.1.1
service ...
This issue has been solved
IPs - 10.1.1.1 and 192.168.1.1.
It might be using 10.1.1.1 to talk to all other clients, which means on those clients, 10.1.1.1 should resolve back to NBUmaster.
But the master may use 192.168.1.1 to talk ...
UATmachine.symantec.com,UAT,Solaris,5.10,2,22
10.1.1.1,production,Solaris,5.10,2,22
(continue this format until all computers are included) ...
in SSIM console:
Monitored Host Name 10.1.1.1
Monitored Host Account Name PC_NAME\LOCAL_PC_USER ... PC_NAME\LOCAL_PC_USER has permissions to read Security log on 10.1.1.1. Can I received collect data from Windows ... this as a user PC_NAME\LOCAL_PC_USER of 10.1.1.1
Add Event log readers snap-in.
Try to connect ...
This issue has been solved