FCIP on Nexus

Hi,
I have to provide a solution to my customer on disaster recovery and SAN-to-SAN Storage Replication Part. (The second DC will be around 400Km far from the main DC)
Q-1)
I have Nexus 7010 and 5596UP in the DC solution. I would like to know whether Nexus can do FCoIP or do i need a MDS switches for this?
If Nexus can do this then whic model, what modules required, what typr of trancevers, and what are the license requried to do the same.
If not, what type of MDS switche? what modules required, what typr of trancevers, and what are the license requried to do the same.
Q-2)
Do we require any specific link? do we require a dedicated link for this? or can i use my exisitng WAN link for this (Bandwidth is <40 Mb only)
if yes, what type of link requried? if yes what would be the suggested bandwidth? (3k-5k users accsing the data, 7-15 Tera data will be on storage)
is there any module on any wan router can accomplish the task? i read cisco 7200 / 7400 series router has FCIP Module (PA-FC-1G). If it support still i need a FCoE swith to convert the FC to IP? or i can directly connect the SAN port to the router module?
regards
Sunny

Can you please post the proper show commands for the fcip interfaces, resp. pc.
what is the error message of the fcip interfaces (also show logging log in general)

Similar Messages

Connecting IBM v7000 to Nexus 5548

20-Sep-2012 16:51 (in response to feisalb)
IBM V7000 with Nexus 5548UP and Nexus 4000 Design/implemetation guide
Hi Guys
I have a question in regards to connecting IBM v7000 directly to Nexus5548.
CAN WE DO THIS?
Our current setup is IBM v7000 -> MDS 9124 -> Nexus 5548.
But our MDS 9124 are out of warranty now and we need to take them out of production. And only way we can do this is if we connect our IBM v7000 fibre ports directly to our Nexus 5548.
Can someone please point me to the right direction any knowledge base articles etc.
Thanks Heaps
Sid

Dear prkrishn
I am working on the Data Center Solution between two Data Center, details underneath
DC 1 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
DC 2 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
With the above mention setup, can I configure FCIP between DC1 & DC2 using Nexus 7009? or I need FCIP capable Switch such as IBM SAN Switch (SAN06-BR), I was wondering if I can configure FCIP on Nexus 7009 DC Switch.
Hoping for your kind response at earliest.
Kind Regards,
Arnold

Interoperability between Cisco Nexus 5548UP and IBM FC3171

Dear Techies,
We have a Cisco Nexus Switch 5548UP already in our environment with DS-SFP-FC8G-SW installed. We are planning to procure IBM Pure Flex Chassis without FC Switch, since we already have Nexus that can provide this facility. But in order to connect IBM Flex with Cisco Nexus we are planning to use IBM FC3171 Switch with IBM 44X1964 Transceivers which will act as a Mediator/Pass Through Switch for connecting IBM and Cisco.
If any expert knows OR have used this scenario, please let me know since I am interested to know if it will work in this scenario or not.
Regards,
Farhan.

Dear prkrishn
I am working on the Data Center Solution between two Data Center, details underneath
DC 1 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
DC 2 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
With the above mention setup, can I configure FCIP between DC1 & DC2 using Nexus 7009? or I need FCIP capable Switch such as IBM SAN Switch (SAN06-BR), I was wondering if I can configure FCIP on Nexus 7009 DC Switch.
Hoping for your kind response at earliest.
Kind Regards,
Arnold

What are the major differences between Nexus 55xx and MDS series w.r.t FC/FCoE/FCIP, scalability etc. ?

Please share any link which tells this and which switch to go with?

In the inital post where I put "
The N7K sees the server MAC in the FIP snooping, it also sees the 5548 as it's FCF. But the 5548 vfc is stuck in "initializing".
I meant to put N4K...not N7K...sorry about that.

Nexus 4000i in blade center H to 5548UP - no Flogi login

I have a fully integrated network in 2 separate data centers built solely on Nexus 5500UP switches that I just got finished designing and implementing. It connects FCoE to all hosts, FCoE from server access 5596UP to a pair of 5596 that act as "SAN" swtiches where I have native FC SFP that connect to XIV storage. In that environement all works great, multi-hop FCoE, NPIV, etc. All zoning and SAN administration is done fully on the N5K 5500 platform. (I even have MDS 9222i sole used for FCIP tunneling on the A and B fabric and that works like a champ too, DCNM sees both data centers as one large A and B fabric with the FCIP tunnels linking them)
The issue is when I introduced a pair of blade centers with N4K switches and a pair of 5548UP switches as their upstream FCF. The documentation isn't rocket science and yet I can't get a FLOGI login. The N7K sees the server MAC in the FIP snooping, it also sees the 5548 as it's FCF. But the 5548 vfc is stuck in "initializing". QoS is there, NXOS is upgraded, etc...I'm stumped and annoyed at this point. DCNM sees the 5548 as part of the fabric and it is a subordinated switch in the fcdomain and once I brought the switch up, all zoning, aliasing, etc was received on the switch...so I know the 5548 can see the fabric. Below are some configs (I cut out what isn't relevant)
5548UP:
Software
BIOS:      version 3.5.0
loader:    version N/A
kickstart: version 5.1(3)N1(1)
system:    version 5.1(3)N1(1)
feature npiv
feature telnet
no feature http-server
feature tacacs+
cfs eth distribute
feature interface-vlan
feature lacp
feature vpc
feature lldp
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
interface port-channel10
description 20Gbps Trunk to CLT-BC1-4001-PD-01 port e1/15 and 16
switchport mode trunk
switchport trunk allowed vlan 310
spanning-tree port type network
interface vfc141
bind mac-address 00:c0:dd:20:50:41
switchport description CLT-BC1 Blade #1
no shutdown
vsan database
vsan 310 interface vfc55
vsan 310 interface vfc141
interface Ethernet1/7
description Trunk to CLT-BC1-4001-PD-01 port e1/15
switchport mode trunk
switchport trunk allowed vlan 310
channel-group 10 mode active
interface Ethernet1/8
description Trunk to CLT-BC1-4001-PD-01 port e1/16
switchport mode trunk
switchport trunk allowed vlan 310
channel-group 10 mode active
CLT-SAC-5548-PD-05# show int vfc 141
vfc141 is trunking
    Bound MAC is 00:c0:dd:20:50:41
    Port description is CLT-BC1 Blade #1
    Hardware is Ethernet
    Port WWN is 20:8c:54:7f:ee:5a:d2:bf
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 310
    Trunk vsans (admin allowed and active) (310)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (310)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Mon Mar 12 21:26:47 2012
CLT-SAC-5548-PD-05# show flogi database
No flogi sessions found.
CLT-SAC-5548-PD-05#show fcdomain
VSAN 310
The local switch is a Subordinated Switch.
Local switch run time information:
        State: Stable
        Local switch WWN:    21:36:54:7f:ee:5a:d2:81
        Running fabric name: 21:36:54:7f:ee:1c:d0:81
        Running priority: 128
        Current domain ID: 0xec(236)
Local switch configuration information:
        State: Enabled
        FCID persistence: Enabled
        Auto-reconfiguration: Disabled
        Contiguous-allocation: Disabled
        Configured fabric name: 20:01:00:05:30:00:28:df
        Optimize Mode: Disabled
        Configured priority: 128
        Configured domain ID: 0x00(0) (preferred)
Principal switch run time information:
        Running priority: 2
Interface                 Role          RCF-reject
vfc55                 Upstream         Disabled
Nexus 4000i switch
Software
BIOS:      version 1.0.37
loader:    version N/A
kickstart: version 4.1(2)E1(1h)
system:    version 4.1(2)E1(1h)
feature telnet
feature tacacs+
feature interface-vlan
feature lacp
feature fip-snooping
policy-map type queuing policy-fcoe-bandwidth
class type queuing 1p7q4t-out-q-default
    bandwidth percent 50
class type queuing 1p7q4t-out-pq1
    bandwidth percent 7
class type queuing 1p7q4t-out-q2
    bandwidth percent 7
class type queuing 1p7q4t-out-q3
    bandwidth percent 7
class type queuing 1p7q4t-out-q4
    bandwidth percent 7
class type queuing 1p7q4t-out-q5
    bandwidth percent 7
class type queuing 1p7q4t-out-q6
    bandwidth percent 7
class type queuing 1p7q4t-out-q7
    bandwidth percent 7
class-map type network-qos class-fcoe
match cos 3
class-map type network-qos class-non-fcoe
match cos 0-2,4-7
policy-map type network-qos policy-fcoe
class type network-qos class-fcoe
    pause no-drop
    mtu 2500
class type network-qos class-non-fcoe
system qos
service-policy type network-qos policy-fcoe
service-policy type queuing output policy-fcoe-bandwidth
vlan 310
fip-snooping enable
interface port-channel10
description 20Gbps Trunk to CLT-SAC-5548-PD-05 port e1/7 and 8
switchport mode trunk
switchport trunk allowed vlan 310
fip-snooping port-mode fcf
spanning-tree port type network
speed 10000
interface Ethernet1/1                 <----the server is in slot 1
switchport mode trunk
spanning-tree port type edge trunk
speed auto
interface Ethernet1/15
description Trunk to CLT-SAC-5548-PD-05 port e1/7
switchport mode trunk
switchport trunk allowed vlan 310
speed 10000
channel-group 10 mode active
interface Ethernet1/16
description Trunk to CLT-SAC-5548-PD-05 port e1/8
switchport mode trunk
switchport trunk allowed vlan 310
speed 10000
channel-group 10 mode active
CLT-BC1-4001-PD-01# show fip-snooping fcf
Legend:
Interface VLAN Active FPMA/ FCMAP      FCF-MAC   Pri   Switch WWN Fabric Name
               Enodes SPMA
por10     310 0      FPMA 0x0efc00 54:7f:ee:5a 128 21:36:54:7f: 21:36:54:7f:
                                    :d2:8a            ee:5a:d2:81 ee:1c:d0:81
CLT-BC1-4001-PD-01# show fip-snooping vlan-discovery
Legend:
      Interface      VLAN          FIP MAC
       Eth1/1         1         00:c0:dd:20:50:41
Any suggestions because I'm stumped!! I'm also attaching a PDF copy of my Visio that shows port by port mapping and configuration for this blade chassis and port-channel 10.
Thanks for the help.
Chris

In the inital post where I put "
The N7K sees the server MAC in the FIP snooping, it also sees the 5548 as it's FCF. But the 5548 vfc is stuck in "initializing".
I meant to put N4K...not N7K...sorry about that.

What is the best practice for QOS in an MDS 9000 environment for the FCIP traffic?

Our storage group is implementing an MDS 9000 FCIP environment. The person configuring the Nexus equipment is asking what QOS markings and bandwidth requirements should be used for the FCIP traffic.
Is there a document that describes the QOS recommendations for MDS FCIP?

Hello
You can change the DB isolation level to Read uncommitted
http://technet.microsoft.com/en-us/library/ms378149(v=sql.110).aspx
or use WITH (NOLOCK)
I do use NOLOCK option for the dirty reads to avoid locks on the tables
Javier Villegas |
@javier_vill | http://sql-javier-villegas.blogspot.com/
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

Nexus 5K - Data Center to Data Center

Hi All,
A scenario was recently presented to me that involved connecting two SANs between two Data Centers. One of the Data Centers is existing and utilizes Nexus 5K switches while the other Data Center will be greenfield and is currently just a shell.
From what I've been reading the Nexus 5K does not support FCIP and I have some concerns regarding the feasibility to perform SAN to SAN over a Service Providers WDM infrastructure; mainly due to cost. More reading suggested that this could not be done with FCoE.
Just wanted to pick everyones brain regarding what solutions are available to interconnect two SANs between Data Centers. The solution would involve using a Service Provider, Ethernet and WDM services are available to both locations.

You can add a pair of MDS9222i in the middle. This will take care of FCIP, DWDM traffic.

Nexus 7000 - Fabric Failure and VOQ

I have been doing some research on the Nexus 7k and from what i am reading the following occurs:
1. Fabric Module Failure - Causes all traffic sent across that fabric modules crossbar to be lost
2. VOQ - protects against lack of buffer availability on the egress interface
Neither of these provide reliable transmission over the crossbar or acknowledgement of data crossing the crossbar fabric.
So my question is, if i have storage traffic (unicast based FCIP) that is crossing the fabric when a fabric module fails, is my understanding correct, that those frames are lost on the portion of the fabric that is controlled by the failed fabric module?
Even though the main fabric itself is intact for other traffic, this still means that I have loss in what is supposed to be a system built for zero-loss to support storage traffic.
Am i way off here or is this accurate.
Thanks.

Thanks for the response. From what i have read the control plane and data plane are completely isolated in the nexus 7k. The supervisor modules control the control plane and the central arbiter and the fabric modules handle the VOQ and the xbar communication.
It works like this as i understand it:
1. packet arrives at the ingress of a line card and is passed on the port asic
2. port asic does its thing and forwards the packet to the replication engine
3. rep engine passes the packet onto the L2 and L3 Forwarding engines - they do their dance and pass the packet on to the fabric engine
4. Fabric Engine and VOQ mgmr consults the central arbiters to get credits to send traffic on the fabric
5. Central Arbiter checks the egress line card to ensure buffer space is available. If its available it grants credit to the fabric engine and VOQ engine to send the packet on the fabric.
The fabric crossbar is BW is determined by the amount of fabric modules installed - 1 FM = 23Gbs x 2. When 2 or more FM are installed to create more Fabric BW, they forwarding across the fabric for unicast traffic acts like a Etherchannel and performs some sort of hashing algorithm to send the packet across the fabric.
Lets say you have a 9216Byte packet and 3 Fabric modules installed. From what i am reading the packet would be broken up into 4 packets, around 2304 Bytes each (i think they might be 2460 can't recall), and passed across the fabric.
So you have 1 large packet, fragmented across the fabric cards, sent to the destination IO card.
While in transit, lets say one of the fabric Modules in the LB group dies. my understanding is the traffic on the trace goes with it.
The traffic is lost in this case since there is no acknowledgement of traffic sent across the fabric. I would think in a high bandwidth situtation this could be a lot of traffic, considering the speeds we are talking about here.
Is this a possibility or am i missing some redundancy here that will protect the traffic that would be lossed crossing the fabric?
Is this the case on the 65k as well for traffic crossing the fabric?
Thanks in advance.
Mike

FCoE VLAN with OTV or FCIP across WAN.

Hello All,
I am wondering how would we extend a FCoE VLAN/VSAN to remote DC.
Can we use the extended VLAN from OTV and use it for FCoE or FCIP to span the SAN using N5K?
I appreciate if someone let me know what are the options to extend the VSAN/SAN across WAN.
Best Regards
Mohammed Khair Khomakho
CCIE Routing and Switching #26682

Sorry just to elaborate on the above question. If I already have OTV on nexus 7k that is used to link between 2 remote sites, can we make use of this existing link to support FCoE? Traditionally we used FCIP on MDS, to link between remote sites to extend our VSAN traffics. So can we use FCoE to run between sites connected by OTV. Thanks.

Why does Android Reader smart zoom not work as described on Google Nexus 7 2013 tablet?

The smart zoom feature in Android Acrobat Reader allows you to double tap on a text column and the reader will zoom up to the column in improve readability. This feature works great on the Samsung Galaxy Note 2 smart phone, but only appears to zoom half way on the Google Nexus 7 2013 tablet.
Is this a bug?
Thanks in advance for your replies.
Regards,
Jim Savitz

Would it be possible for you to share the problematic pdf and OS information with us at [email protected] so that we may investigate?
Thanks,
Adobe Reader Team

Diff b/w Nexus 5548P and 5548UP

What is the
Diff b/w Nexus 5548P and 5548UP
regards.

Hi,
A UP or Unified ports allow you to configure ports as Ethernet, native Fibre Channel or Fibre Channel over Ethernet (FCoE) ports. By default, the ports are Ethernet ports but you can change the port mode to Fibre Channel on the following unified ports:
Any port on the Cisco Nexus 5548UP switch or the Cisco Nexus 5596UP switch.
The ports on the Cisco N55-M16UP expansion module that is installed in a Cisco Nexus 5548P switch.
More details:
http://www.cisco.com/web/techdoc/dc/reference/cli/nxos/commands/l2/port.html
Comapre 5548 and 5548:
http://www.cisco.com/en/US/products/ps9670/prod_models_comparison.html
./Abhinav

Error on nexus 7k series " operation failed.the fabric is already locked"

getting following error on nexus 7k series switch: error is " operation failed.the fabric is already locked", while removing ntp commands (no ntp server 10.101.1.1) from switch. Please help.

I had the same error message, only in my situation Outlook would only open successfully every 4 or 5 attempts. When Outlook would open (versus just hanging at the splash screen), I would get two dialog boxes with the warning/error message.
After I clicked okay I could get into Outlook.
Previously I experienced this problem running my Office 2010 client with my Exchange 2007 mailbox on my old laptop. The problem followed my mailbox through an Exchange 2010 migration (so new Exchange org), client upgrade to Outlook 2013, and a new
laptop (so I knew it wasn't a corrupt profile). This led me to the conclusion that it was a corrupt item(s) in my mailbox.
To resolve the issue, I archived *everything* in my mailbox to a PST file, ran SCANPST to fix the corruption, and then uploaded everything back into my Exchange mailbox one folder at a time, stopping after each folder to close and restart Outlook so I could
narrow down which folder had the corrupt item if the problem recurred. I'm happy to say my issue is now resolved.

Can i return my nexus 7 it keeps restarting but i bought it 9 months ago

so i bought a nexus 7 about 9 months ago i was excited to own my first tablet so i ignored the restarting in the beginning i figured google should send a patch of some sort but till this day it actually got worse i have a receipt its a really faded but i have it i also have the box.
So main question can i return it?

Hey mark79,
Welcome to the BestBuy forums! You ask a great question. avm5689 has answered most of it and gave you the information you needed.
Just for further assistance I am going to link you to the troubleshooting/helpful tip area for nexus 7 tablets
https://support.google.com/nexus/answer/4582729?hl=en
You may also join the Nexus Google Forums and ask there for further assistance.
https://productforums.google.com/forum/#!forum/nexus
Just curious, is this restarting constantly, or only when you do a certain item ( such as updating )
Are you able to boot your device into safe mode?
Ensure your device's screen is on, then press & hold the Power button.
Touch & hold the Power off option in the dialog box.
Touch OK in the following dialog to start safe mode.
Does the problem persist while in safe mode?
A good piece of advice though is that there are some 3rd party apps that really mess up the nexus operating system so just a FYI.
If this only restarts while the wifi is in 5ghz that is a well known issue as well.
I am not affiliated with Best Buy nor have I ever been employed by Best Buy. All of my thoughts and posts are of my own opinion and personal experience.
I may not always know the right answer, but I will always tell you what I do know. I also do free computer analysis and consultation via private message.

SWR10 Not Syncing with Android Lollipop (5.0.1) on Nexus 6

I got my SWR10 3 days ago.
At first it was synced up to my Nexus 7 (2013) tablet (Also running Android 5.0.1) where it worked fine and tracked every correctly. Sleep was tracked correctly to the next day.
The next day I left the tablet at home as I went to go buy my Nexus 6. Connected the smartband to the Nexus 6 and none of the offline data synced. I put this down to me changing devices and decided to see how it faired today.
Today however, it did not track my sleep overnight. It has not tracked any steps all day. But the smartband is connected to the phone and does work as i've been using it for the media remote mode throughout the day. The phone hasn't been out of range of the smartband either as it's been in my pocket all day.
I have a suscpicion that this might be caused by a compatability issue with LifeLog and Android 5.0.1 as every time I open it up I get an error message saying the app had crashed and gives me the option to report the crash. I've left a screenshot of the bug report below.
Solved!
Go to Solution.

I've figured the solution out myself... Well a workaround at least for the time being. It seems the component of the app that's crashing is the logger.
It appears this needs to be running to sync the data from the smartband and whenever you open the app this component crashes and toggles itself off in the settings.
Toggle it back on and press the home key to leave the application without returning to the timeline view and it should stay running in the background.
All the data it hadn't synced reappeared so the smartband must have kept the data.
This seems to be a workaround whilst Sony fix whatever the issue is.

Samsung Galaxy Nexus Android 4.2 Update

When will Verizon approve the Android 4.2 update for the Samsung Galaxy Nexus? The slowness of Verizon to approve updates is inexcusable! And to that I'll say, "I'm done!" I am so disgusted with Verizon and their inability to provide updates to what is supposed to be a "Nexus" device. It's not like they have to manipulate around manufacturer software. It's pure Google operating system. Load and test the drivers for CDMA and LTE and then launch the update. At the MOST that should take no more than 2 weeks! Since I have had my Nexus on Verizon, I have not recieved a single update prior to 2 months! Android 4.2 update from Android 4.1 is so miniscule and, might I add, required no additional new drivers, so what is the hold up Verizon? Where is the Android 4.2 update? And, yeah, I know some techy out there is going to say, " well why don't you just jailbreak and load it yourself?" Because I shouldn't HAVE to jailbreak my phone. It's not a matter of can I do it, it's why can't I do it without jailbreaking from Verizon? They sold this phone initially by claiming it to be a "pure Nexus" device and it's been nothing of the kind ever since! So I say, "I'm done!" That means that when my contract is up, I'm return to AT&T! They have upgraded the towers in the area that I live and my friends on AT&T say their signals are even better than Verizon's. AT&T's new LTE towers download at faster speeds than Verizon's too. I would have happily stayed with Verizon if they would have only taken the Pure Nexus experience seriously!
To those who have stated that I've said this for Jelly Bean 4.1, you are correct! The only reason I'm still here is because of the hefty penalty Verizon will charge me for terminating my contract early. My contract doesn't expire until December 2013 so it would be a rather hefty penalty to pay. But Android 4.2 has confirmed that Verizon refuses to change their position on slow updates, so when my contract is up (as I believe I stated on 4.1), you won't see REDNIBKRAM on Verizon anymore!
It appears as though the Verizon "love freaks" just can't seem to get the message. I'm not saying that the updates aren't difficult, I'm saying that if Verizon chooses to use CDMA technology over GSM and that requires them to jump through hoops to get updates completed, then they should have NEVER agreed to carry a "pure Nexus" device, or at the very least, should have NEVER advertised the device as such. My whole point is that Verizon LIED TO ME and told me that my phone was a "pure Nexus" device when I purchased it and switched from a GSM phone company (AT&T) when, in fact, they knew that I would NOT be getting updates directly from Google as the GSM versions of the SGN do. At the very least, if Verizon really wanted to make this right, they would offer to allow anyone with a SGN phone who was lied to when they purchased it to exit from their existing contract without penalty, so we can purchase a "TRUELY PURE NEXUS" phone direct from Google or provide us with a choice of another phone (Windows Phone, iPhone, etc.) without having to renew a 2 year contract.
All I'm saying is that if Verizon won't or can't update the phones they themselves advertised as a "pure Nexus" phone, then they should make it right to the people they lied to.

I didn't go back to AT&T for JB in August because the of VERY HEFTY penalty I will have to pay for cancelling my contract early and I got the Android 4.1 JB update. Once I received the update and because the the penalty, I decided to give BIGRED another change at the next update. I thought, "maybe it was such a huge update that they really needed to make sure everything was done right." So, now here we are waiting for the 4.2.1 update and I'm still getting the same response from BIGRED as I got for JB 4.0 update. It's quite clear that VZ DOESN'T CARE about customer satisfaction. They use the excuse that they want their network to be the best and they want their phones to operate with little or no problems, yet when problems ARE discovered, it takes them months to send out the updates that Google has already released months prior. I have discussed updates with Verizon, Google and Samsung support personnel. I have even contacted Verizon Corporate and I fully understand the process by which updates are done, and believe me when I say that the update process at VZ is in serious need of restructuring. Especially when it comes to Android devices. But as far as this Android 4.2.1 update is concerned, I have spoken with Google and they have informed me that there was NO changes made to the operating system that would affect the CDMA or LTE drivers on the Verizon Samsung Galaxy Nexus, so there should be no reason why Verizon would not want to release the update. The small changes (additions) to the operating system would in no way affect the communications on VZ. So why hasn't VZ released this update yet. Corporate says they need to test the software to ensure it doesn't affect communications on their network, yet Google hasn't changed anything in the operating system that would, so what are they testing? VZ may have the better network, but CARRIER EXPERIENCE ISN'T ALL ABOUT THE BEST CONNECTION. It's about customer SATISFACTION and not receiving updates on a pure NEXUS device in a timely manner is inexcusable and in NO WAY SATISFYING! So when my contract is up, I will be returning to AT&T or giving T-Mobile a try on a pure Nexus device with no contract!

FCIP on Nexus

Similar Messages

Maybe you are looking for