MS Surface Pro w/ third party magnetic swipe USB Device (this was suggested by several people)
Morgan Mcleod: HP Elitepad with expansion jacket for integrated swipe card function.
http://www.emobilepos.com/portofolio/hp-elitepad-with-windows/
http://www.emobilepos.com/portofolio/hp-elitepad-retail-expansion-jacket/
IP : 169.254.24.7
Username : Liebert
Password : Liebert
The PDF standard does not have Superscript the same as Microsoft Word so you will have to do this manually
E.g. if you are making 10th , write the whole word and select th and choose edit properties and change from the defaults to below
Got to
Config/settings/advanced/url-mappings
Then add the following :
/tag/[name] -> /?tag=[name] 301
When trying to restore from a backup exec backup to a Virtual machine , the dropdown option “Convert to Virtual Machine from Point in Time” is Greyed Out.
Make sure when you backup the Machine you backup Everything including System State or this option will not be available
Also make sure one of your backup jobs are not backing up the machine through a Vcenter. This is how backup Exec manages VM level backup jobs for fulling restoring a VM
Enabled SSH Login on your VCenter Appliance ( this can be done through the GUI or via Direct Console Access )
Run the below commands replacing username and snmp servername
snmp.set --users username/-/-/none
snmp.set --communities liability
snmp.set --v3targets snmpservername@161/username/none/trap
This command will show you all the current settings
snmp.get
If I understand correctly, these are 4x SC220 enclosures for the SC8000 SAN. Although there is no IO interruption to the SAN, ideally this should be done during scheduled outage. Ensure that backup on current CML LUNs have been taken prior to this activity. The steps below need to be precisely followed to avoid outage and issues.
Required materials:
Here’s the plan and tasks:
Ensure that current SAS cabling is according to figure 1 below.
The 2x SAS cards and 2x full-height PCI brackets come with the SC8000 systems. Note that this will cause a split-second front-end IO disruption when the LUNs failover to the other controller. Monitoring system will generate alerts and there will be a call from Dell Pro Support. It is transparent to servers. Current CML SAN layout is attached
Sequence:
After new SAS card installation and PCI cards re-arrangement, the cards layout should be:
Reference:
Figure 2: SC8000 rear port layout.
Adding three enclosures are going to be done in two phases:
Single chain two enclosures side A
Figure 3: Removal of Chain 1: Side A SAS connections from current topology.
Figure 4: Chain 1: Side A new topology.
Single chain two enclosures side B
Figure 5: Chain 1: Side B new topology.
Figure 6: 2 controllers, 2 chains, 2 sides, 5 enclosures topology
You will be taking out and in excess of after completion:
It might be worth checking if these still need to be RDM’s. This was previously used for older versions of VMDK’s could only use 2TB , now with esx 5.5 and Virtual Machine hardware 10 this is upped to 62TB
Changed Pysical RDM to Virtaul RDM to VMDK’s
Use the webclient for this
1) Shutdown the server
2) Upgrade the Virtual Hardware to 10
3) Remove the Physical RDM Lun
4) Re-Add the Lun as Virtual
5) Power on server
6) Storage VMotion to New SAN
FYI Virtual RDM’s cannot be resized without shutting down the machine unlike Physical
Deploy vSRX – VMware Workstation
RE – Routing Engine
— Manages the PFE
— Maintins Routing Tables
— Manages the Packet Forwarding Engine
PFE – Packet Forward Engine
— Is incharge of Policing , Stateless Firewall Filtering and CoS implemented by forwarding plane
— Forarding Plane Central Procesing contains the PFE
They are seperated in Juniper ( Control and Forwarding Planes ) to benifit speed and reduce bottlenecks -> https://www.juniper.net/techpubs/en_US/junos9.3/topics/concept/psd-control-and-forwarding-plane-in-separate-chassis.html
– Forwarding table is stored on both
-Routing Table ( stored on Control Plane ) Populate Forwarding Table
–Import Policys filter items doing to Routing Table
Routing Policy
Must have a then doesn’t need a from
Juniper also split software processes in Modules
Same base source code for all Boxes
Ctrl-A = Left All
Ctrl-U = Delete All
Ctrl-W = Backspace
Default Location for Configs are in /home/user
Default Location for logs /var/logs/
WIP Config = Canidate Configurations
Active Config = After Commit
version 12.1X44-D35.5;
groups {
node0 {
system {
host-name A;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.50.1/24;
}
}
}
}
}
node1 {
system {
host-name SB;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 192.168.50.2/24;
}
}
}
}
}
}
apply-groups "${node}";
system {
time-zone Australia/Brisbane;
root-authentication {
encrypted-password "";
}
name-server {
8.8.8.8;
8.8.4.4;
}
services {
ssh;
web-management {
http;
}
dhcp {
pool 192.168.30.0/24 {
address-range low 192.168.30.100 high 192.168.30.200;
router {
192.168.30.1;
}
propagate-settings vlan.100;
}
}
ntp {
server 129.250.35.250;
}
}
chassis {
cluster {
reth-count 3;
redundancy-group 0 {
node 0 priority 200;
node 1 priority 1;
}
redundancy-group 1 {
node 0 priority 200;
node 1 priority 1;
interface-monitor {
ge-0/0/14 weight 255;
ge-5/0/14 weight 255;
ge-0/0/15 weight 255;
ge-5/0/15 weight 255;
}
}
redundancy-group 2 {
node 0 priority 254;
node 1 priority 1;
}
}
}
interfaces {
traceoptions {
file interface-debug;
flag all;
}
ge-0/0/11 {
unit 0 {
encapsulation ppp-over-ether;
}
}
ge-0/0/13 {
gigether-options {
redundant-parent reth2;
}
}
ge-0/0/14 {
gigether-options {
redundant-parent reth0;
}
}
ge-0/0/15 {
gigether-options {
redundant-parent reth1;
}
}
ge-5/0/13 {
gigether-options {
redundant-parent reth2;
}
}
ge-5/0/14 {
gigether-options {
redundant-parent reth0;
}
}
ge-5/0/15 {
gigether-options {
redundant-parent reth1;
}
}
fab0 {
fabric-options {
member-interfaces {
ge-0/0/2;
}
}
}
fab1 {
fabric-options {
member-interfaces {
ge-5/0/2;
}
}
}
pp0 {
unit 0 {
ppp-options {
pap {
local-name "";
local-password "";
passive;
}
lcp-max-conf-req 0;
}
pppoe-options {
underlying-interface ge-0/0/11.0;
idle-timeout 0;
auto-reconnect 10;
client;
}
family inet {
mtu 1492;
negotiate-address;
}
}
}
reth0 {
vlan-tagging;
redundant-ether-options {
redundancy-group 1;
}
unit 100 {
vlan-id 100;
family inet {
address 192.168.30.1/24;
}
}
}
reth1 {
redundant-ether-options {
redundancy-group 1;
}
unit 0 {
encapsulation ppp-over-ether;
}
}
reth2 {
vlan-tagging;
redundant-ether-options {
redundancy-group 2;
}
unit 100 {
vlan-id 100;
family inet {
address 192.168.30.1/24;
}
}
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop pp0.0;
}
}
class-of-service {
host-outbound-traffic {
ieee-802.1 {
default be;
}
}
}
security {
tcp-mss {
all-tcp {
mss 1300;
}
}
}
nat {
source {
rule-set students_srcnat {
from zone Student;
to zone untrust;
rule students_srcnat_1 {
match {
destination-address 0.0.0.0/0;
}
then {
source-nat {
interface;
}
}
}
}
rule-set staff_srcnat {
from zone Internal;
to zone untrust;
rule staff_srcnat_1 {
match {
destination-address 0.0.0.0/0;
}
then {
source-nat {
interface;
}
}
}
}
rule-set wireless_srcnat {
from zone Wireless;
to zone untrust;
rule wireless_srcnat_1 {
match {
destination-address 0.0.0.0/0;
}
then {
source-nat {
interface;
}
}
}
}
}
}
policies {
from-zone Internal to-zone untrust {
policy default-permit {
match {
source-address any;
destination-address any;
application any;
}
then {
permit;
}
}
}
from-zone Student to-zone untrust {
policy student-internet {
match {
source-address any;
destination-address any;
application any;
}
then {
permit;
}
}
}
from-zone Wireless to-zone untrust {
policy wireless-internet {
match {
source-address any;
destination-address any;
application any;
}
then {
permit;
}
}
}
from-zone Internal to-zone Internal {
policy test-1 {
match {
source-address any;
destination-address any;
application any;
}
then {
permit;
}
}
}
}
zones {
security-zone External {
interfaces {
reth1.0;
}
}
security-zone Internal {
address-book {
address NEC <IPofNEC>/32;
}
interfaces {
reth0.100 {
host-inbound-traffic {
system-services {
dhcp;
all;
}
protocols {
all;
}
}
}
}
}
security-zone untrust {
host-inbound-traffic {
system-services {
http;
ssh;
}
}
interfaces {
pp0.0;
ge-0/0/11.0;
}
}
}
}Copyright © 2017 Welcome to Pariswells.com All rights reserved. Theme by Laptop Geek. Privacy Policy